[
https://issues.apache.org/jira/browse/CASSANDRA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561602#comment-15561602
]
Stefan Podkowinski commented on CASSANDRA-7296:
-----------------------------------------------
bq. 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.
This. Most people are not even aware of this behavior and get confused by
different results. There definitely should be a way to query individual nodes
deterministically even if it's "just" for troubleshooting.
> 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)
