You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Coli (JIRA)" <ji...@apache.org> on 2014/05/16 13:18:37 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=13999609#comment-13999609 ]
Robert Coli commented on CASSANDRA-6760:
----------------------------------------
As a meta-comment, many new operators probably presume that disablethrift-like methods which disable the port the client connects to do this, because they don't think of reads via the storage protocol.
> 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.2#6252)