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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/21 00:48:53 UTC

[jira] [Commented] (CASSANDRA-2568) Write only mode

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

Jonathan Ellis commented on CASSANDRA-2568:
-------------------------------------------

Superceded by CASSANDRA-4839
                
> Write only mode
> ---------------
>
>                 Key: CASSANDRA-2568
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2568
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Priority: Minor
>
> Allow a node to receive writes (which are relatively cheap) but not reads (random io).  The purpose is to allow a major compaction or repair to be run on a node that is under too much load for this be safely done "live".  Marking a node as down by disabling gossip is good enough in some cases(for major compaction).  But for repairs is insufficient, since hints will build back up once I repeat the process on the next node.
> This is presumably a rather complicated change in to gossip to accommodate the new state.  I am also concerned of the effects of having different numbers of nodes available for write and read quorums.
> See also: http://www.mail-archive.com/dev@cassandra.apache.org/msg02240.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira