[
https://issues.apache.org/jira/browse/CASSANDRA-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-20523:
----------------------------------------
Fix Version/s: 5.1-alpha1
(was: 5.x)
Since Version: 5.1-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/6f79207c34e2d828e798a8a96df67aeaea2a45a1
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Improve metadata log catch up with inter-DC mutation forwarding
> ---------------------------------------------------------------
>
> Key: CASSANDRA-20523
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20523
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 5.1-alpha1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We currently try to catch up from the sender when we see a newer epoch in the
> message. If the message has been forwarded by a peer in the local DC it might
> not yet have caught up. We should always try to catch up from the originator
> of the message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
