incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vivek Mishra <mishra.v...@gmail.com>
Subject Re: Broken pipe with Thrift
Date Tue, 24 Dec 2013 07:52:04 GMT
Hi Steven,
One question, which is confusing , it's a server side issue or client side?

-Vivek




On Tue, Dec 24, 2013 at 12:30 PM, Vivek Mishra <mishra.vivs@gmail.com>wrote:

> Hi Steven,
> Thanks for your reply. We are using version 1.2.9.
>
> -Vivek
>
>
> On Tue, Dec 24, 2013 at 12:27 PM, Steven A Robenalt <srobenal@stanford.edu
> > wrote:
>
>> Hi Vivek,
>>
>> Which release are you using? We had an issue with 2.0.2 that was solved
>> by a fix in 2.0.3.
>>
>>
>> On Mon, Dec 23, 2013 at 10:47 PM, Vivek Mishra <mishra.vivs@gmail.com>wrote:
>>
>>> Also to add. It works absolutely fine on single node.
>>>
>>> -Vivek
>>>
>>>
>>> On Tue, Dec 24, 2013 at 12:15 PM, Vivek Mishra <mishra.vivs@gmail.com>wrote:
>>>
>>>> Hi,
>>>> I have a 6 node, 2DC cluster setup. I have configured consistency level
>>>> to QUORUM.  But very often i am getting "Broken pipe"
>>>> com.impetus.client.cassandra.CassandraClientBase
>>>> (CassandraClientBase.java:1926) - Error while executing native CQL
>>>> query Caused by: .
>>>> org.apache.thrift.transport.TTransportExceptionjava.net.SocketException:
>>>> Broken pipe
>>>>        at
>>>> org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport
>>>> java:147)
>>>> at
>>>> org.apache.thrift.transport.TFramedTransport.flush(TFramedTransport.jav
>>>> a:156)
>>>> at
>>>> org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:65)
>>>> at
>>>> org.apache.cassandra.thrift.Cassandra$Client.send_execute_cql3_query(Ca
>>>> ssandra.java:1556)
>>>> at
>>>> org.apache.cassandra.thrift.Cassandra$Client.execute_cql3_query(Cassand
>>>> ra.java:1546)
>>>>
>>>>
>>>> I am simply reading few records from a column family(not huge amount of
>>>> data)
>>>>
>>>> Connection pooling and socket time out is properly configured. I have
>>>> even modified
>>>> read_request_timeout_in_ms
>>>> request_timeout_in_ms
>>>> write_request_timeout_in_ms  in cassandra.yaml to higher value.
>>>>
>>>>
>>>> any idea? Is it an issue at server side or with client API?
>>>>
>>>> -Vivek
>>>>
>>>
>>>
>>
>>
>> --
>> Steve Robenalt
>> Software Architect
>>  HighWire | Stanford University
>> 425 Broadway St, Redwood City, CA 94063
>>
>> srobenal@stanford.edu
>> http://highwire.stanford.edu
>>
>>
>>
>>
>>
>>
>

Mime
View raw message