-
Notifications
You must be signed in to change notification settings - Fork 217
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
Add @SingleThread annotation to dissect processor #5463
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Taylor Gray <[email protected]>
It seems that the main reason this is not thread safe is because the Lines 26 to 32 in fee636c
Might there be other bugs with this behavior? |
I'm not sure. There could be, but so far this processor works fine with a single thread. Don't you think this is a good short term fix though? Seems like the refactor to avoid this mutation may be larger |
Yea, that may be a lot. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@graytaylor0 Good find! I remember seeing a customer issue where dissect processor returns weird results a few times out of like a million processed events. This might have been the root cause.
Description
Dissect processor is not thread safe. Added "@SingleThread" annotation
Issues Resolved
Resolves #5462
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.