[ 
https://issues.apache.org/jira/browse/CASSANDRA-11537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644889#comment-17644889
 ] 

Paulo Motta commented on CASSANDRA-11537:
-----------------------------------------

Thanks for the feedback. I agree this should be a rare case, and you can always 
use other JMX tools to inspect the server.

If this turns out to be a problem, we could introduce a {{--skip-init-check}} 
flag to skip this safer behavior.

> Give clear error when certain nodetool commands are issued before server is 
> ready
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11537
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11537
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Observability, Local/Startup and Shutdown
>            Reporter: Edward Capriolo
>            Priority: Low
>              Labels: lhf
>
> As an ops person upgrading and servicing Cassandra servers, I require a more 
> clear message when I issue a nodetool command that the server is not ready 
> for it so that I am not confused.
> Technical description:
> If you deploy a new binary, restart, and issue nodetool 
> scrub/compact/updatess etc you get unfriendly assertion. An exception would 
> be easier to understand. Also if a user has turned assertions off it is 
> unclear what might happen. 
> {noformat}
> EC1: Throw exception to make it clear server is still in start up process. 
> :~# nodetool upgradesstables
> error: null
> -- StackTrace --
> java.lang.AssertionError
>     at org.apache.cassandra.db.Keyspace.open(Keyspace.java:97)
>     at 
> org.apache.cassandra.service.StorageService.getValidKeyspace(StorageService.java:2573)
>     at 
> org.apache.cassandra.service.StorageService.getValidColumnFamilies(StorageService.java:2661)
>     at 
> org.apache.cassandra.service.StorageService.upgradeSSTables(StorageService.java:2421)
> {noformat}
> EC1: 
> Patch against 2.1 (branch)
> https://github.com/apache/cassandra/compare/trunk...edwardcapriolo:exception-on-startup?expand=1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to