danny0405 commented on issue #18424: URL: https://github.com/apache/hudi/issues/18424#issuecomment-4159694286
> To fix this, we can potentially change the flushDisruptor function NOT to call disruptorQueue.close() directly, but implementing a function to spin-wait until the disruptor buffer is fully consumed. In other words, just does the "spin-wait part" but not the "terminate thread" part. Looks reasonable as long as we have a good way to collect the finished threads. Does it mean the disrupt thread is closed after the buffer is fully consumed? -- 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]
