-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] SerializeConcatHostBuffersDeserializeBatch may have thread issues #1179
Comments
jlowe
added
bug
Something isn't working
? - Needs Triage
Need team to review and classify
labels
Nov 20, 2020
sameerz
added
P0
Must have for release
and removed
? - Needs Triage
Need team to review and classify
labels
Nov 24, 2020
Here is the stack trace that we saw in the integration tests that led to us reverting the previous PR.
|
tgravescs
pushed a commit
to tgravescs/spark-rapids
that referenced
this issue
Nov 30, 2023
[auto-merge] bot-auto-merge-branch-23.06 to branch-23.08 [skip ci] [bot]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#1174 fixed an issue initializing the columnar batch row count on a degenerate batch that was row-only, but since that change is necessary to fix an issue it implies threads are trying to access the batch while it is being created. The concern is if there could be multiple threads trying to create a normal GPU batch simultaneously and end up leaking all but the last one recorded.
It's also disconcerting that #1165 needed to be reverted, so we need to understand what the threading implications are here and make sure the serializer is doing the correct thing in light of multiple thread access.
The text was updated successfully, but these errors were encountered: