[
https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-11323:
---------------------------------------
Fix Version/s: 4.0.2
3.11.12
3.0.26
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/84eb1b8c85371e1d73bb8a0e60393de8bf4af28b
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into 3.0 84eb1b8c85371e1d73bb8a0e60393de8bf4af28b and merged into
3.11, 4.0 and trunk
> 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
> Fix For: 3.0.26, 3.11.12, 4.0.2
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
