cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Coli <rc...@eventbrite.com>
Subject Re: TTransportException (java.net.SocketException: Broken pipe)
Date Mon, 21 Jul 2014 23:47:02 GMT
On Mon, Jul 21, 2014 at 8:07 AM, Bhaskar Singhal <bhaskarsinghal@yahoo.com>
wrote:

> I have not seen the issue after changing the commit log segment size to
> 1024MB.
>

Yes... your insanely over-huge commitlog will be contained in fewer files
if you increase the size of segments.... that will not make it any less of
an insanely over-huge commitlog which indicates systemic failure in your
application's use of Cassandra. Congratulations on masking your actual
issue with your configuration change.

"
Pool Name                    Active   Pending      Completed   Blocked  All
time blocked
FlushWriter                       6        10          12442
1              2940
"

1/4 attempts to flush blocked waiting for resources, and you have 6 actives
flushes and 10 pending, because YOU'RE WRITING TOO FAST.

As a meta aside, I am unlikely to respond to further questions of yours
which do not engage with what I have now told you three or four times, that
YOU'RE WRITING TOO FAST.

=Rob

Mime
View raw message