You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2014/02/24 22:21:19 UTC

[jira] [Commented] (CASSANDRA-6760) Nodetool command to disable reads

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

Brandon Williams commented on CASSANDRA-6760:
---------------------------------------------

Not the first time I've heard this feature requested, so I agree it's good.  That said, it's complicated, because while adding the gossip state is easy, this is going to have implications reaching all the way into the consistency level.

> Nodetool command to disable reads
> ---------------------------------
>
>                 Key: CASSANDRA-6760
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6760
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Priority: Minor
>
> There is no way to stop a node from accepting reads and still be part of the ring. 
> This will be helpful in case node does not bootstrap properly and we need to run node tool rebuild to fetch the data. 
> The node can use gossip to propagate this fact to other nodes so that they don't forward reads to it. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)