[
https://issues.apache.org/jira/browse/CASSANDRA-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009817#comment-13009817
]
Stu Hood commented on CASSANDRA-2364:
-------------------------------------
What about tracking write latencies using a separate metric set? Alternatively,
if the snitch had less than RF scores, it could choose a random node.
Choosing unbalanced write coordinators for counters would only cause imbalances
pre-replication: if repair is running frequently (repair-on-write, read-repair,
AES, etc), the load is balanced according to the tokens, as usual.
I agree that adding things that are really counter specific is not healthy,
unless they also help to set us up for other atomic features in the future.
> Record dynamic snitch latencies for counter writes
> --------------------------------------------------
>
> Key: CASSANDRA-2364
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2364
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Priority: Minor
> Labels: counters
> Fix For: 0.8
>
>
> The counter code chooses a single replica to coordinate a write, meaning that
> it should be subject to dynamic snitch latencies like a read would be. This
> already works when there are reads going on, because the dynamic snitch read
> latencies are used to pick a node to coordinate, but when there are no reads
> going on (such as during a backfill) the latencies do not adjust.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
