[
https://issues.apache.org/jira/browse/CASSANDRA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555951#comment-15555951
]
Jon Haddad edited comment on CASSANDRA-7296 at 10/7/16 6:57 PM:
----------------------------------------------------------------
I'd like to resurrect this. There's cases where an operator needs to know
exactly what's on a specific node. CL.COORDINATOR_ONLY is useful for debugging
all sorts of production issues. Dynamic snitch makes CL=ONE not an effective
way of determining what's on a specific node.
was (Author: rustyrazorblade):
I'd like to resurrect this. There's cases where an operator needs to know
exactly what's on a specific node. CL.COORDINATOR_ONLY is useful for debugging
all sorts of production issues.
> Add CL.COORDINATOR_ONLY
> -----------------------
>
> Key: CASSANDRA-7296
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7296
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Tupshin Harper
>
> For reasons such as CASSANDRA-6340 and similar, it would be nice to have a
> read that never gets distributed, and only works if the coordinator you are
> talking to is an owner of the row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
