[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-11323: --- Reviewers: Ariel Weisberg, Benjamin Lerer, Brandon Williams (was: Ariel Weisberg, Benjamin Lerer) > 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
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-11323: --- Status: Ready to Commit (was: Review In Progress) > 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
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-11323: --- Reviewers: Ariel Weisberg, Benjamin Lerer, Benjamin Lerer (was: Ariel Weisberg, Benjamin Lerer) Ariel Weisberg, Benjamin Lerer, Benjamin Lerer (was: Ariel Weisberg) Status: Review In Progress (was: Patch Available) > 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
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ 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
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11323: --- Status: Ready to Commit (was: Patch Available) > 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: Trivial > 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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-3.11.txt > 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: Trivial > 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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-3.0.txt > 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: Trivial > Labels: fallout > Attachments: 11323-2.2.txt, 11323-3.0.txt, 11323-3.0.txt, > 11323-3.11.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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-trunk.txt > 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: Trivial > 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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. Scott Andreas updated CASSANDRA-11323: - Component/s: Observability > 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: Observability >Reporter: T Jake Luciani >Assignee: Boris Onufriyev >Priority: Trivial > Labels: fallout > Attachments: 11323-2.2.txt, 11323-3.0.txt, 11323-3.11.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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-trunk.txt > 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, 11323-3.0.txt, 11323-3.11.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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-3.0.txt > 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, 11323-3.0.txt, 11323-3.11.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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-3.11.txt > 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, 11323-3.0.txt, 11323-3.11.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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11323: --- Reviewers: Ariel Weisberg Reviewer: Ariel Weisberg > 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 > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Status: Patch Available (was: Open) > 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 > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Onufriyev updated CASSANDRA-11323: Attachment: 11323-2.2.txt > 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 > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information
[ 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)