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] Commented: (CASSANDRA-768) "safe mode" for nodes so that they do not participate in reads until hinted handoff is complete
Date Fri, 05 Feb 2010 22:22:28 GMT

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

Jonathan Ellis commented on CASSANDRA-768:
------------------------------------------

This is not a good fit for cassandra.

> "safe mode" for nodes so that they do not participate in reads until hinted handoff is
complete
> -----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-768
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-768
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Robert Coli
>            Priority: Minor
>
> Summary :
> When using ConsistencyLevel.ONE for read performance reasons, stale data can be served
by a node which has been temporarily unavailable. When a node has been unavailable for some
time and other nodes have queued updates for it via hinted handoff, it would be operationally
useful to be able to configure the node to not participate in read traffic until the hinted
handoff process is complete. A "safe mode" would offer operators a greater consistency guarantee
across all nodes without the per-read performance tradeoff of a higher ConsistencyLevel. This
"safe mode" concept might also be applicable to nodes undergoing "repair" processes, for example
in the case of on-disk data corruption or loss.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message