rionmonster commented on issue #1855: URL: https://github.com/apache/fluss/issues/1855#issuecomment-3453112526
@polyzos I've gone ahead and put together a proposed fix for the issue which followed a common concurrency pattern used throughout the Fluss code base (basically reducing two separate reads/references for our internal, volatile list into a single reference per iteration). The code change itself was pretty simple and straight-forward as the bulk of the work was consistently reproducing the issue in the first place, which I've added a unit test for as well. The test really just consists of two separate threads which will oscillate add/removal operations resulting in the null pointer exception. After introducing the fix itself, I just updated the test to assert that we _don't_ have an exception that gets thrown. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
