[
https://issues.apache.org/jira/browse/CASSANDRA-16877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16877:
----------------------------------------
Fix Version/s: (was: 4.0.x)
4.0.1
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/b8242730918c2e8edec83aeafeeae8255378125d
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks. Agreed about the tests, so committed (with one nit addressed and one
swerved) to 4.0 in {{b8242730918c2e8edec83aeafeeae8255378125d}} and merged up
to trunk.
> High priority internode messages which exceed the large message threshold are
> dropped
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16877
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16877
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 4.0.1
>
>
> Currently, there is an assumption that internode messages whose verb has
> priority P0 will always fit within a single messaging frame. While this is
> usually the case, on occasion it is possible that this assumption does not
> hold. One example is gossip messages during the startup shadow round, where
> in very large clusters the digest ack can contain all states for every peer.
> In this scenario, the respondent fails to send the ack which may lead to the
> shadow round and, ultimately, the startup failing.
>
> We could tweak the shadow round acks to minimise the message size, but a more
> robust solution would be to permit high priority messages to be sent on the
> large messages connection when necessary.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
