rionmonster commented on issue #2091: URL: https://github.com/apache/fluss/issues/2091#issuecomment-3614106377
@swuferhong After digging into this a bit more, the issue may already be addressed on the Flink-side per [this commit roughly 2 weeks ago](https://github.com/apache/flink/commit/56a56a0f194d51bddd1b3da3ad7ca39746035fe3) that addresses the underlying `SerializedThrowable` class and its potential for these cascading errors ([see discussion here](https://github.com/apache/flink/pull/27186#discussion_r2547013397)): > I think current PR could help to resolve the StackOverflowError via introducing the alreadySeen set to deduplicate. > ... > And the dead lock problem could happen when calling InstantiationUtil.serializeObject(exception); > The simplest way to resolve this is synchronizing the function like: We _could_ introduce a similar guard on the Fluss side to prevent this cascading problem as a safety check, although I'm not sure if it's necessary as the issue seems to be addressed upstream in Flink. Thoughts? -- 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]
