I have this anytime I try to switch to "hsha" since 0.8.

Always kept "sync" for this reason. Thought I was alone with this bug since I never had any clue about this on the mailing list.

So +1.

Alain


2013/8/13 Christopher Wirt <chris.wirt@struq.com>

Hello,

I was trying out the hsha thrift server implementation and found that I get a fair amount of these appearing in the server logs.

ERROR [Selector-Thread-9] 2013-08-13 15:39:10,433 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

ERROR [Selector-Thread-9] 2013-08-13 15:39:11,499 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

ERROR [Selector-Thread-9] 2013-08-13 15:39:11,695 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

ERROR [Selector-Thread-9] 2013-08-13 15:39:12,562 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

ERROR [Selector-Thread-1] 2013-08-13 15:39:12,660 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

ERROR [Selector-Thread-9] 2013-08-13 15:39:13,496 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

ERROR [Selector-Thread-9] 2013-08-13 15:39:14,281 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the client side?

Anyone seen this message before? know what it means? or issues it could hide?

https://issues.apache.org/jira/browse/CASSANDRA-4573

in the comments suggests it might be a 10 client timeout

but looking at JMX client stats the max value for read/write/slice is well below 10secs

Iím using 1.2.8 on centos

Cheers,

Chris