incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Luciani <jak...@gmail.com>
Subject Re: HsHa
Date Wed, 14 Aug 2013 14:02:23 GMT
This is technically a Thrift message not Cassandra, it happens when a
client hangs up without closing the socket.
You should be able to silence it by raising the class specific log level
see log4j-server.properties as an example


On Wed, Aug 14, 2013 at 9:59 AM, Alain RODRIGUEZ <arodrime@gmail.com> wrote:

> @Commiters/Experts,
>
> Does this sound like a bug or like 4 PEBCAKs to you ? Should we raise a
> JIRA ?
>
> Alain
>
>
> 2013/8/14 Keith Wright <kwright@nanigans.com>
>
>> Same here on 1.2.4.
>>
>> From: Romain HARDOUIN <romain.hardouin@urssaf.fr>
>> Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
>> Date: Wednesday, August 14, 2013 3:36 AM
>> To: "user@cassandra.apache.org" <user@cassandra.apache.org>
>> Subject: Re: HsHa
>>
>> The same goes for us.
>>
>> Romain
>>
>> Alain RODRIGUEZ <arodrime@gmail.com> a écrit sur 13/08/2013 18:10:05 :
>>
>> > De : Alain RODRIGUEZ <arodrime@gmail.com>
>> > A : user@cassandra.apache.org,
>> > Date : 13/08/2013 18:10
>> > Objet : Re: HsHa
>> >
>> > 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
>>
>
>


-- 
http://twitter.com/tjake

Mime
View raw message