[
https://issues.apache.org/jira/browse/CASSANDRA-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714355#comment-13714355
]
Peter Haggerty commented on CASSANDRA-4573:
-------------------------------------------
We may be seeing this behavior in 1.2.6. I haven't enabled debug but we are
definitely seeing a correlation between groups of 'Read an invalid frame size
of 0' messages (dozens at a time) during the same second that we're seeing
"large" (10 seconds or more) 'GC for ConcurrentMarkSweep' events.
On a 9 node cluster we see this anywhere from 1 to 9 times a day.
> HSHA doesn't handle large messages gracefully
> ---------------------------------------------
>
> Key: CASSANDRA-4573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4573
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Vijay
> Attachments: repro.py
>
>
> 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}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
