[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Lerer updated CASSANDRA-11323: --------------------------------------- Status: Patch Available (was: Ready to Commit) > 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 > Components: Legacy/Observability > Reporter: T Jake Luciani > Assignee: Boris Onufriyev > Priority: Low > Labels: fallout > Attachments: 11323-2.2.txt, 11323-3.0.txt, 11323-3.0.txt, > 11323-3.11.txt, 11323-3.11.txt, 11323-trunk.txt, 11323-trunk.txt > > > {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 (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org