cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2568) Write only mode
Date Fri, 12 Aug 2011 21:47:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-2568:
--------------------------------------

    Fix Version/s:     (was: 1.0)

Brandon, what do you think?  What would need to happen for this to work?

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message