Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of marcelo@s1mbi0se.com.br
 designates 209.85.213.177 as permitted sender)
MIME-Version: 1.0
Date: Wed, 18 Jun 2014 12:13:59 -0300
Message-ID: 
 <CAAX2xq54D2AmnqX56q5-A93Pobui+sQq5LoD24m5ahRsPhQVcQ@mail.gmail.com>
Subject: Batch of prepared statements exceeding specified threshold
From: Marcelo Elias Del Valle <marcelo@s1mbi0se.com.br>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e01538e6cb3143604fc1db5bc

--089e01538e6cb3143604fc1db5bc
Content-Type: text/plain; charset=UTF-8

I have a 10 node cluster with cassandra 2.0.8.

I am taking this exceptions in the log when I run my code. What my code
does is just reading data from a CF and in some cases it writes new data.

 WARN [Native-Transport-Requests:553] 2014-06-18 11:04:51,391
BatchStatement.java (line 228) Batch of prepared statements for
[identification1.entity, identification1.entity_lookup] is of size 6165,
exceeding specified threshold of 5120 by 1045.
 WARN [Native-Transport-Requests:583] 2014-06-18 11:05:01,152
BatchStatement.java (line 228) Batch of prepared statements for
[identification1.entity, identification1.entity_lookup] is of size 21266,
exceeding specified threshold of 5120 by 16146.
 WARN [Native-Transport-Requests:581] 2014-06-18 11:05:20,229
BatchStatement.java (line 228) Batch of prepared statements for
[identification1.entity, identification1.entity_lookup] is of size 22978,
exceeding specified threshold of 5120 by 17858.
 INFO [MemoryMeter:1] 2014-06-18 11:05:32,682 Memtable.java (line 481)
CFS(Keyspace='OpsCenter', ColumnFamily='rollups300') liveRatio is
14.249755859375 (just-counted was 9.85302734375).  calculation took 3ms for
1024 cells

After some time, one node of the cluster goes down. Then it goes back after
some seconds and another node goes down. It keeps happening and there is
always a node down in the cluster, when it goes back another one falls.

The only exceptions I see in the log is "connected reset by the peer",
which seems to be relative to gossip protocol, when a node goes down.

Any hint of what could I do to investigate this problem further?

Best regards,
Marcelo Valle.

--089e01538e6cb3143604fc1db5bc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I have a 10 node cluster with cassandra 2.0.8.</div><=
div><br></div><div>I am taking this exceptions in the log when I run my cod=
e. What my code does is just reading data from a CF and in some cases it wr=
ites new data.</div>
<div><br></div><div>=C2=A0WARN [Native-Transport-Requests:553] 2014-06-18 1=
1:04:51,391 BatchStatement.java (line 228) Batch of prepared statements for=
 [identification1.entity, identification1.entity_lookup] is of size 6165, e=
xceeding specified threshold of 5120 by 1045.</div>
<div>=C2=A0WARN [Native-Transport-Requests:583] 2014-06-18 11:05:01,152 Bat=
chStatement.java (line 228) Batch of prepared statements for [identificatio=
n1.entity, identification1.entity_lookup] is of size 21266, exceeding speci=
fied threshold of 5120 by 16146.</div>
<div>=C2=A0WARN [Native-Transport-Requests:581] 2014-06-18 11:05:20,229 Bat=
chStatement.java (line 228) Batch of prepared statements for [identificatio=
n1.entity, identification1.entity_lookup] is of size 22978, exceeding speci=
fied threshold of 5120 by 17858.</div>
<div>=C2=A0INFO [MemoryMeter:1] 2014-06-18 11:05:32,682 Memtable.java (line=
 481) CFS(Keyspace=3D&#39;OpsCenter&#39;, ColumnFamily=3D&#39;rollups300=
9;) liveRatio is 14.249755859375 (just-counted was 9.85302734375). =C2=A0ca=
lculation took 3ms for 1024 cells</div>
<div><br></div><div>After some time, one node of the cluster goes down. The=
n it goes back after some seconds and another node goes down. It keeps happ=
ening and there is always a node down in the cluster, when it goes back ano=
ther one falls.</div>
<div><br></div><div>The only exceptions I see in the log is &quot;connected=
 reset by the peer&quot;, which seems to be relative to gossip protocol, wh=
en a node goes down.</div><div><br></div><div>Any hint of what could I do t=
o investigate this problem further?</div>
<div><br></div><div>Best regards,</div><div>Marcelo Valle.</div></div>

--089e01538e6cb3143604fc1db5bc--