[
https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686996#comment-16686996
]
Ariel Weisberg commented on CASSANDRA-11323:
--------------------------------------------
Thanks [~BorisO]. 2.2 is getting critical bug fixes only so this can only go
into 3.0, 3.11, and trunk. Can you make patches for those three versions?
The log message could probably be more informative like "%d bytes required for
next commit log segment, but only %d bytes available. " It also seems like we
want this to occur for everything except ignore? Or maybe even then? I think
the only concern would be if we log it repeatedly when ignore is the policy due
to some high volume exception. You could use the NoSpamLogger to avoid that
issue.
Another issue is that this error is generated even if the exception is
something else. So we should probably have the log message specify that free
space is not necessarily the cause of this exception. And if we are getting
even more transparent, maybe we should specify the commit log directory path
just so people at a glance know what volume is in use.
> 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
> Assignee: Boris Onufriyev
> Priority: Trivial
> Labels: fallout
> Attachments: 11323-2.2.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
