cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
Date Wed, 09 Mar 2016 15:32:40 GMT

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

T Jake Luciani updated CASSANDRA-11323:
---------------------------------------
    Labels: fallout  (was: )

> When node runs out of commitlog space you get poor log information
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-11323
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11323
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Priority: Trivial
>              Labels: fallout
>
> {code}
> ERROR [PERIODIC-COMMIT-LOG-SYNCER] 2016-03-08 20:27:33,899 StorageService.java:470 -
Stopping gossiper
> WARN  [PERIODIC-COMMIT-LOG-SYNCER] 2016-03-08 20:27:33,899 StorageService.java:377 -
Stopping gossip by operator request
> INFO  [PERIODIC-COMMIT-LOG-SYNCER] 2016-03-08 20:27:33,899 Gossiper.java:1463 - Announcing
shutdown
> {code}
> That's all you get when a node runs out of commit log space. 
> We should explicitly callout the fact the commitlog is out of disk.  I see that in the
commit log error handler but after it shuts down. So I think it's never getting written before
shutdown.



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

Mime
View raw message