pnowojski commented on pull request #18475: URL: https://github.com/apache/flink/pull/18475#issuecomment-1025585234
Your efforts didn't go for nothing. We deeply appreciate that you have reported and analysed this bug. A half year ago another user reported similar symptoms, but neither he nor we were able to track it down back then. Analysing it was definitely the most valuable and important part of this issue. Apart of the things that I've already commented, there are a couple of other smaller (stylistic) issues. Also we will potentially need to deduplicate this code with a fix for FLINK-25827. To speed things up, I will take over your commit, drop the tests as (we will need to reimplement them in https://issues.apache.org/jira/browse/FLINK-25869 ), while merging most of your production code as it is. > I couldn't see how can the callback get the obsolete object. Dirty inconsistence between CPU cache cannot last that long. The callback will see the correct object. I'm afraid you still don't quite get it. If you are further curious about the subject, please search around for some other resources. -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
