cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12461) Add hooks to StorageService shutdown
Date Fri, 26 Aug 2016 08:29:21 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438651#comment-15438651
] 

Alex Petrov commented on CASSANDRA-12461:
-----------------------------------------

bq.  I was unable to reproduce the 'LOGBACK: No context' error (I ran it as DSE in our CCM)
with either 'ccm stop' and a 'kill XXX'. What were you doing there to trigger that bug?

You can only see it when attached to terminal (i.e. running {{cassandra -f}}) and force-quitting
it. I suppose since logging is already shut down it can not write to the file, so can only
output through {{STDOUT}}... 

bq. it runs pre shutdown hooks it clears the list so they do not run twice

That definitely fixes the issue, although I still think that we should solve it by (maybe)
removing a shutdown hook on successful drain ([CASSANDRA-12509])

> Add hooks to StorageService shutdown
> ------------------------------------
>
>                 Key: CASSANDRA-12461
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12461
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Anthony Cozzie
>            Assignee: Anthony Cozzie
>         Attachments: 0001-CASSANDRA-12461-add-C-support-for-shutdown-runnables.patch
>
>
> The JVM will usually run shutdown hooks in parallel.  This can lead to synchronization
problems between Cassandra, services that depend on it, and services it depends on.  This
patch adds some simple support for shutdown hooks to StorageService.
> This should nearly solve CASSANDRA-12011



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message