[
https://issues.apache.org/jira/browse/CASSANDRA-12011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-12011:
---------------------------------------
Assignee: (was: Benjamin Lerer)
> Logback shutdown hook races with StorageServiceShutdownHook
> -----------------------------------------------------------
>
> Key: CASSANDRA-12011
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12011
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joel Knighton
> Priority: Minor
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> In {{StorageService}}, we add a JVM shutdown hook called
> {{StorageServiceShutdownHook}} that shuts down gossip and flushes writes for
> non durable keyspaces, among other things.
> In {{logback.xml}}, we add a JVM shutdown hook that tears down logback
> resources.
> Since JVM shutdown hooks are started concurrently, the logback shutdown hook
> almost always completes during the {{StorageServiceShutdownHook}}, which
> means that any log statements in this hook will not work since the logback
> resources have been torn down.
> This makes debugging the {{StorageServiceShutdownHook}} challenging. We
> should do our own logback teardown that does not run until after the
> completion of any Cassandra-oriented JVM shutdown hooks such as the
> {{StorageServiceShutdownHook}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
