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

maxwellguo commented on CASSANDRA-15406:
----------------------------------------

[~rha] Thank you for your reply, The mode of the node is a good way to get the 
node's joining/leaving status. But what i mean is just the percentage of the 
progress . 

When we do bootstrap, the node is doing streaming for some days, but people 
don't know the rate of progress for streaming,80% ? 90% ? increasing  or just 
stuck at 90% progress? or during the state of rebuild secondary index after all 
data streaming finished? 

Querying log and doing some calculation is a way but not intuitive. So I think 
a command for nodetool to show the rate is intuitive and it  is easy to find 
problems when the rate keep at  50% for some hours ( for example ).

I can take over this issue latter to finish this and I think this work have 
meaning.


> Add command to show the progress of data streaming and index build 
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-15406
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15406
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Streaming, Legacy/Streaming and Messaging, 
> Tool/nodetool
>            Reporter: maxwellguo
>            Priority: Normal
>
> I found that we should supply a command to show the progress of streaming 
> when we do the operation of bootstrap/move/decommission/removenode. For when 
> do data streaming , noboday knows which steps there program are in , so I 
> think a command to show the joing/leaving node's is needed .



--
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

Reply via email to