cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11537) Give clear error when certain nodetool commands are issued before server is ready
Date Fri, 22 Apr 2016 12:41:12 GMT


Sylvain Lebresne commented on CASSANDRA-11537:

bq. I think the user wants the stack trace. IE if my job is to script a cluster wide compaction
using nodetool, the 'compact' command should let me know that this failed. The best is likely
the non 0 result and message bubble all the way out to the user.

I completely agree that we want a non 0 return status for the command on such error, but we
can totally have that without a trace.

> Give clear error when certain nodetool commands are issued before server is ready
> ---------------------------------------------------------------------------------
>                 Key: CASSANDRA-11537
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Edward Capriolo
>            Assignee: Edward Capriolo
>            Priority: Minor
>              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
>     at org.apache.cassandra.service.StorageService.getValidKeyspace(
>     at org.apache.cassandra.service.StorageService.getValidColumnFamilies(
>     at org.apache.cassandra.service.StorageService.upgradeSSTables(
> {noformat}
> EC1: 
> Patch against 2.1 (branch)

This message was sent by Atlassian JIRA

View raw message