Re: How to interpret uninterpreted `nodetool compact` java stack trace in 3.11.0

2017-10-08 Thread Ridley Submission
Ok thanks for your reply. I do believe this one is already in JIRA: https://issues.apache.org/jira/browse/CASSANDRA-13897?jql=text%20~%20%22nodetool%20flush%20compact%22 Regards, Ridley NB: The debug.log provides only minimal extra information above what is in that JIRA ticket. The name of the

Re: How to interpret uninterpreted `nodetool compact` java stack trace in 3.11.0

2017-10-08 Thread Jeff Jirsa
Likely failed but you’d need to check the full logs to be positive Assertion errors typically should be reported on the JIRA - you’ve encountered a situation the developer didn’t think was possible so it’s aborted, but we need to know that you encountered it so we can fix it Please open the ji

How to interpret uninterpreted `nodetool compact` java stack trace in 3.11.0

2017-10-08 Thread Ridley Submission
Hi Everyone, I wonder how do we interpret this error message? Does it mean that the compaction failed? Is this an error I should be concerned about? Thanks, Ridley cassandra@server:$ nodetool compact error: null -- StackTrace -- java.lang.AssertionError at org.apache.cassandra.cache.ChunkCache