Details
-
Improvement
-
Status: Resolved
-
High
-
Resolution: Fixed
-
None
-
Quality Assurance
-
Challenging
-
Description
CASSANDRA-8457 introduced asynchronous networking to internode messaging, but there have been several follow-up endeavours to improve some semantic issues. CASSANDRA-14503 and CASSANDRA-13630 are the latest such efforts, and were combined some months ago into a single overarching refactor of the original work, to address some of the issues that have been discovered. Given the criticality of this work to the project, we wanted to bring some more eyes to bear to ensure the release goes ahead smoothly. In doing so, we uncovered a number of issues with messaging, some of which long standing, that we felt needed to be addressed. This patch widens the scope of CASSANDRA-14503 and CASSANDRA-13630 in an effort to close the book on the messaging service, at least for the foreseeable future.
The patch includes a number of clarifying refactors that touch outside of the net.async package, and a number of semantic changes to the net.async packages itself. We believe it clarifies the intent and behaviour of the code while improving system stability, which we will outline in comments below.
https://github.com/belliottsmith/cassandra/tree/messaging-improvements
Attachments
Attachments
Issue Links
- causes
-
CASSANDRA-17981 Restore internode custom tracing
-
- Resolved
-
- contains
-
CASSANDRA-3017 add a Message size limit
-
- Resolved
-
-
CASSANDRA-9289 Recover from unknown table when deserializing internode messages
-
- Resolved
-
- fixes
-
CASSANDRA-10619 disallow streaming operations while upgrading
-
- Resolved
-
- is duplicated by
-
CASSANDRA-15088 PagingTest failure on trunk
-
- Resolved
-
-
CASSANDRA-15222 BufferedDataOutputStreamPlus.write() should use FastByteOperations.copy()
-
- Resolved
-
- supercedes
-
CASSANDRA-14575 Reevaluate when to drop an internode connection on message error
-
- Resolved
-
- mentioned in
-
Page Loading...