cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4573) HSHA doesn't handle large messages gracefully
Date Thu, 01 Aug 2013 22:57:49 GMT


Tyler Hobbs commented on CASSANDRA-4573:

After a quick check, it looks like the CASSANDRA-5582 implementation also doesn't enforce
the max frame size.
> HSHA doesn't handle large messages gracefully
> ---------------------------------------------
>                 Key: CASSANDRA-4573
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>         Attachments:
> 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:

View raw message