[ https://issues.apache.org/jira/browse/CASSANDRA-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2568. --------------------------------------- Resolution: Duplicate > 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