bfreuden commented on issue #1518: URL: https://github.com/apache/helix/issues/1518#issuecomment-847691668
@mebe thanks for pointing at this ticket and comment: I was not aware of it. Although it sounds strange to me, I am ready to accept the ``SubscribeChangeEventProcessor`` can't be daemonized. I have the feeling we need a way to terminate an Helix application properly though. Otherwise it means that the application has to be killed and I don't know if that will trigger a proper "finalization of all handlers" (just quoting the comment here, I don't understand what it means). In my experience, once the JVM has decided to stop, there's not much you can do... even in the shutdown hooks. That's why I've always considered it best to have a "clean shutown" function so the application can schedule its own shutdown properly, without any rush. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
