cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10447) Async logging configuration doesn't result in data flushing when shutdown hook runs
Date Tue, 06 Oct 2015 16:05:26 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paulo Motta updated CASSANDRA-10447:
------------------------------------
    Reviewer: Paulo Motta

> Async logging configuration doesn't result in data flushing when shutdown hook runs
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10447
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10447
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>             Fix For: 3.0.0 rc2
>
>
> Stefania discovered that tests that don't produce a lot of log output end up producing
0 debug output to files because the data is not flushed as part of the shutdown hook. I traced
through and it looks like the shutdown hook doesn't actually invoke code that does anything
useful. It shuts down an executor service in the logging context but doesn't call stop on
any appenders.
> A hackish thing we can do is use a status listener to collect all the appenders and then
stop them when the shutdown hook runs. Even adding a small delay to the shutdown hook (no
code changes on our part) would in let the async appender flush in 90% of cases.
> We still need to fix it for test which uses a different config file and for which a small
delay is not desirable.



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

Mime
View raw message