[CASSANDRA-10206] Incorrect handling of end-of stream leading to infinite loop in streaming session

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.10, 2.2.2, 3.0 beta 2

Environment

cassndra 2.1.8 12 nodes cluster in two DC, with enabled ssl encryption.

• Severity: Normal
• Assignee: Unassigned Assign to me
• Reporter: Alexey Burylov

Reviewers

Yuki Morishita

• Created: 27/Aug/15 11:17
• Updated: 16/Apr/19 09:30
• Resolved: 01/Sep/15 22:02

Description

StreamMessage.deserialize (StreamMessage.java:63) function return null when receive end of stream for ReadableByteChannel.read () function. IncomingMessageHandler.run (ConnectionHandler.java:257) interpreting null - as unsupported message and ignore it. It resulting infinite loop when IncomingMessageHandler try to read message from closed steram, and deserialize always return null - to indicate close stream.

It not happen on normal socket, because when normal socket closed it throw IOException. But happen from time to time when iner-node ssl encryption enabled.

I'm attach two tread dump from one node with two infinity lopped thread with id 614 and 583