cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6760) Nodetool command to disable reads
Date Mon, 24 Feb 2014 22:56:26 GMT

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

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

That's not a bad idea, though it won't *guarantee* anything, and you'd have to be using the
dsnitch (though nearly everyone is at this point.)  [~tjake] says it already works this way
even though we both agree the code says otherwise. heh.

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

Mime
View raw message