lhotari commented on issue #10289: URL: https://github.com/apache/pulsar/issues/10289#issuecomment-823971603
> No, I couldn’t see any stack trace. I think it was just the JVM default exception handler when the thread is terminated. I added printing of the stacktrace in #10304 . > I also cannot reproduce always, though I’ve seen it few times. I think we should prob just add a catch Throwable in there and it should fix it. I didn't yet add any new catches. I expect that #10304 changes will help find the underlying issue. > > One other minor thing that is reproducible is there seems to be always a 5 sec delay when the executors are being shut down. It seems like we’re always letting some operation to time out. This is expected behavior. For Netty Event Loop Shutdown, there's a quiet time parameter. It's 2 seconds by default. I have increased it to use a fraction of the configured `brokerShutdownTimeoutMs` with the maximum value of 5 seconds. https://github.com/apache/pulsar/blob/152d1e69d16b510521003a33ea877ae33f0ce8e5/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/BrokerService.java#L794-L803 Previously there was no delay since the shutdown didn't wait for the event loops to close at all. The default quiet time is 2 seconds and shutdown timeout 15 seconds in Netty. Those values were used, but the asynchronous return value was ignored. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
