[CASSANDRA-4573] HSHA doesn't handle large messages gracefully

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Severity: Normal
• Assignee: Pavel Yaskevich
• Reporter: Tom Hobbs

Authors

Pavel Yaskevich

Reviewers

Tom Hobbs

• Tester: Tom Hobbs
• Created: 23/Aug/12 18:44
• Updated: 16/Apr/19 09:32
• Resolved: 06/Aug/13 22:22

Description

HSHA doesn't seem to enforce any kind of max message length, and when messages are too large, it doesn't fail gracefully.

With debug logs enabled, you'll see this:

DEBUG 13:13:31,805 Unexpected state 16

Which seems to mean that there's a SelectionKey that's valid, but isn't ready for reading, writing, or accepting.

Client-side, you'll get this thrift error (while trying to read a frame as part of recv_batch_mutate):

TTransportException: TSocket read 0 bytes