You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Vivek Mishra <vi...@yahoo.com> on 2013/12/24 10:54:01 UTC
Broken pipe : Cassandra 1.2.9
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(TIOStreamTransportjava:147)
at org.apache.thrift.transport.TFramedTransport.flush(TFramedTransport.java:156)
at
org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:65)
at
org.apache.cassandra.thrift.Cassandra$Client.send_execute_cql3_query(Cassandra.java:1556)
at
org.apache.cassandra.thrift.Cassandra$Client.execute_cql3_query(Cassandra.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.
It works fine with single node.
any idea? Is it an issue at server side or with client API?
-Vivek
Re: Broken pipe : Cassandra 1.2.9
Posted by Vivek Mishra <vi...@yahoo.com>.
Hi,
Thanks. retry is only option? On server side is it possible to configure such retries?
-Vivek
On Tuesday, December 24, 2013 7:58 PM, Jason Wee <pe...@gmail.com> wrote:
Hmm.. Broken pipe sounds like the existing connection is disconnected. Try reestablish connection again to the cluster node?
/Jason
On Tue, Dec 24, 2013 at 5:54 PM, Vivek Mishra <vi...@yahoo.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(TIOStreamTransportjava:147)
>at org.apache.thrift.transport.TFramedTransport.flush(TFramedTransport.java:156)
>at
>org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:65)
>at
>org.apache.cassandra.thrift.Cassandra$Client.send_execute_cql3_query(Cassandra.java:1556)
>at
>org.apache.cassandra.thrift.Cassandra$Client.execute_cql3_query(Cassandra.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.
>
>
>
>It works fine with single node.
>
>any idea? Is it an issue at server side or with client API?
>
>
>-Vivek
>
Re: Broken pipe : Cassandra 1.2.9
Posted by Jason Wee <pe...@gmail.com>.
Hmm.. Broken pipe sounds like the existing connection is disconnected. Try
reestablish connection again to the cluster node?
/Jason
On Tue, Dec 24, 2013 at 5:54 PM, Vivek Mishra <vi...@yahoo.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(TIOStreamTransportjava:147)
>
> at org.apache.thrift.transport.TFramedTransport.flush(TFramedTransport.java:156)
> at
> org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:65)
> at
>
> org.apache.cassandra.thrift.Cassandra$Client.send_execute_cql3_query(Cassandra.java:1556)
> at
>
> org.apache.cassandra.thrift.Cassandra$Client.execute_cql3_query(Cassandra.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.
>
>
>
> It works fine with single node.
>
> any idea? Is it an issue at server side or with client API?
>
>
> -Vivek
>