[
https://issues.apache.org/jira/browse/KAFKA-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619671#comment-14619671
]
Jason Gustafson commented on KAFKA-2319:
----------------------------------------
Seems like there might be a race condition with onControllerResignation getting
invoked concurrently from shutdown and from another thread (such as in the
zookeeper session expiration listener). In any case, the implementation of
KafkaScheduler.shutdown in trunk now appears to explicitly allow multiple
shutdown attempts (following the patch for KAFKA-1760), so I think this might
not be an issue any longer.
> After controlled shutdown: IllegalStateException: Kafka scheduler has not
> been started
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-2319
> URL: https://issues.apache.org/jira/browse/KAFKA-2319
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Rosenberg
>
> Running 0.8.2.1, just saw this today at the end of a controlled shutdown. It
> doesn't happen every time, but I've seen it several times:
> {code}
> 2015-07-07 18:54:28,424 INFO [Thread-4] server.KafkaServer - [Kafka Server
> 99], Controlled shutdown succeeded
> 2015-07-07 18:54:28,425 INFO [Thread-4] network.SocketServer - [Socket
> Server on Broker 99], Shutting down
> 2015-07-07 18:54:28,435 INFO [Thread-4] network.SocketServer - [Socket
> Server on Broker 99], Shutdown completed
> 2015-07-07 18:54:28,435 INFO [Thread-4] server.KafkaRequestHandlerPool -
> [Kafka Request Handler on Broker 99], shutting down
> 2015-07-07 18:54:28,444 INFO [Thread-4] server.KafkaRequestHandlerPool -
> [Kafka Request Handler on Broker 99], shut down completely
> 2015-07-07 18:54:28,649 INFO [Thread-4] server.ReplicaManager - [Replica
> Manager on Broker 99]: Shut down
> 2015-07-07 18:54:28,649 INFO [Thread-4] server.ReplicaFetcherManager -
> [ReplicaFetcherManager on broker 99] shutting down
> 2015-07-07 18:54:28,650 INFO [Thread-4] server.ReplicaFetcherThread -
> [ReplicaFetcherThread-0-95], Shutting down
> 2015-07-07 18:54:28,750 INFO [Thread-4] server.ReplicaFetcherThread -
> [ReplicaFetcherThread-0-95], Shutdown completed
> 2015-07-07 18:54:28,750 INFO [ReplicaFetcherThread-0-95]
> server.ReplicaFetcherThread - [ReplicaFetcherThread-0-95], Stopped
> 2015-07-07 18:54:28,750 INFO [Thread-4] server.ReplicaFetcherThread -
> [ReplicaFetcherThread-0-98], Shutting down
> 2015-07-07 18:54:28,791 INFO [Thread-4] server.ReplicaFetcherThread -
> [ReplicaFetcherThread-0-98], Shutdown completed
> 2015-07-07 18:54:28,791 INFO [ReplicaFetcherThread-0-98]
> server.ReplicaFetcherThread - [ReplicaFetcherThread-0-98], Stopped
> 2015-07-07 18:54:28,791 INFO [Thread-4] server.ReplicaFetcherManager -
> [ReplicaFetcherManager on broker 99] shutdown completed
> 2015-07-07 18:54:28,819 INFO [Thread-4] server.ReplicaManager - [Replica
> Manager on Broker 99]: Shut down completely
> 2015-07-07 18:54:28,826 INFO [Thread-4] log.LogManager - Shutting down.
> 2015-07-07 18:54:30,459 INFO [Thread-4] log.LogManager - Shutdown complete.
> 2015-07-07 18:54:30,463 WARN [Thread-4] utils.Utils$ - Kafka scheduler has
> not been started
> java.lang.IllegalStateException: Kafka scheduler has not been started
> at kafka.utils.KafkaScheduler.ensureStarted(KafkaScheduler.scala:114)
> at kafka.utils.KafkaScheduler.shutdown(KafkaScheduler.scala:86)
> at
> kafka.controller.KafkaController.onControllerResignation(KafkaController.scala:350)
> at
> kafka.controller.KafkaController.shutdown(KafkaController.scala:664)
> at
> kafka.server.KafkaServer$$anonfun$shutdown$8.apply$mcV$sp(KafkaServer.scala:285)
> at kafka.utils.Utils$.swallow(Utils.scala:172)
> at kafka.utils.Logging$class.swallowWarn(Logging.scala:92)
> at kafka.utils.Utils$.swallowWarn(Utils.scala:45)
> at kafka.utils.Logging$class.swallow(Logging.scala:94)
> at kafka.utils.Utils$.swallow(Utils.scala:45)
> at kafka.server.KafkaServer.shutdown(KafkaServer.scala:285)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
