You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "A. Sophie Blee-Goldman (Jira)" <ji...@apache.org> on 2021/04/21 22:38:00 UTC

[jira] [Created] (KAFKA-12706) Consider adding reason and source of error in APPLICATION_SHUTDOWN

A. Sophie Blee-Goldman created KAFKA-12706:
----------------------------------------------

             Summary: Consider adding reason and source of error in APPLICATION_SHUTDOWN
                 Key: KAFKA-12706
                 URL: https://issues.apache.org/jira/browse/KAFKA-12706
             Project: Kafka
          Issue Type: Improvement
          Components: streams
            Reporter: A. Sophie Blee-Goldman


At the moment when a user opts to shut down the application in the streams uncaught exception handler, we just send a signal to all members of the group who then shut down. If there are a large number of application instances running it can be annoying and time consuming to locate the client that hit this error.

It would be nice if we could let each client log the exception that triggered this, and possibly also the client who requested the shutdown. That will make it much easier to identify the problem, and figure out which set of logs to look into for further information



--
This message was sent by Atlassian Jira
(v8.3.4#803005)