[
https://issues.apache.org/jira/browse/CASSANDRA-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532946#comment-16532946
]
Aleksey Yeschenko commented on CASSANDRA-14555:
-----------------------------------------------
That might be true, but I share [~beobal]'s concern here. I don't think it was
perfectly right to introduce the default change so late in the minor cycle in
3.0.17.
Can we revert from 3.0 and 3.11 please? And apply the suggested mitigations to
trunk?
Thanks.
> Verify effect of CASSANDRA-14252 on streaming endpoint selection
> ----------------------------------------------------------------
>
> Key: CASSANDRA-14555
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14555
> Project: Cassandra
> Issue Type: Task
> Components: Streaming and Messaging
> Reporter: Sam Tunnicliffe
> Priority: Major
> Fix For: 4.x
>
>
> CASSANDRA-14252 makes a slight change to {{DynamicEndpointSnitch}} so that it
> is somewhat more likely a replica in a remote DC is contacted when replicas
> in the local DC are considered degraded. This seems reasonable on the read
> path, but it could also affect selection of endpoints for streaming and cross
> DC streaming is probably something that operators want to control more
> tightly. To be clear, I’m not 100% sure that this is actually an issue, but
> I’d like to have some investigation into it before we ship a change to
> default behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
