apurtell commented on PR #7363: URL: https://github.com/apache/hbase/pull/7363#issuecomment-3427298036
> So maybe we should check depth of the stack trace? In netty there are some tricks around this area, if the future is complete synchronously all the time and makes a very deep call stack trace, it will force schedule an asynchronous task to prevent stack overflow and also reduce the blocking execution time. The potential depth of the stack is out of our control. We are providing a client to an application that is developed by an independent team. So the move of internalFlush and the potentially synchronous downstream completions it may invoke is definitely the right move here. -- 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]
