[
https://issues.apache.org/jira/browse/KAFKA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658510#comment-14658510
]
Gwen Shapira commented on KAFKA-2405:
-------------------------------------
It is supported to create KafkaServer by instantiating the class directly
(without going though Kafka.main). We use it in our tests (I think), and sounds
like LinkedIn uses this in production.
So System.exit of anything below this level sounds like a problem.
> KafkaHealthCheck kills the JVM in handleSessionEstablishmentError
> -----------------------------------------------------------------
>
> Key: KAFKA-2405
> URL: https://issues.apache.org/jira/browse/KAFKA-2405
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: jaikiran pai
> Assignee: jaikiran pai
> Fix For: 0.8.3
>
>
> The current code in KafkaHealthCheck in trunk does this:
> {code}
> override def handleSessionEstablishmentError(error: Throwable): Unit = {
> fatal("Could not establish session with zookeeper", error)
> System.exit(-1)
> }
> {code}
> thus terminating the JVM. A session establishment error shouldn't cause the
> JVM to terminate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
