[ https://issues.apache.org/jira/browse/CASSANDRA-16877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403967#comment-17403967 ]
Caleb Rackliffe commented on CASSANDRA-16877: --------------------------------------------- +1 w/ minor nits [here|https://github.com/beobal/cassandra/commit/045844bab6a175fe6c02d1398c3a33a81a0a2a9d#r55367210] and [here|https://github.com/beobal/cassandra/commit/045844bab6a175fe6c02d1398c3a33a81a0a2a9d#r55367841]. The couple test failures I see don't look related/appear in other live 4.0 branches. > 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.x > > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org