Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAALK=TM-7qRMLfwbLw6csen0qMFR6Lw+kAjGOH4ko+ckhPHLqA@mail.gmail.com>
References: 
 <CAALK=TM-7qRMLfwbLw6csen0qMFR6Lw+kAjGOH4ko+ckhPHLqA@mail.gmail.com>
Date: Tue, 6 Oct 2015 21:05:29 +0530
Message-ID: 
 <CAFbS8c-Nq5E-kWpLAdds_S1ArQz4oc96R0nCwf65+7rXNtkcOQ@mail.gmail.com>
Subject: Re: java.lang.IllegalArgumentException: Mutation of X bytes is too
 large for the maxiumum size of Y
From: Kiran mk <coolkiran2006@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e012947843c8bbc05217161e1

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

Do you see more dropped mutation messages in nodetool tpstats output.
On Oct 6, 2015 7:51 PM, "George Sigletos" <sigletos@textkernel.nl> wrote:

> Hello,
>
> I have been frequently receiving those warnings:
>
> java.lang.IllegalArgumentException: Mutation of 35141120 bytes is too
> large for the maxiumum size of 33554432
>  at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:221)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:383)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:363)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at org.apache.cassandra.db.Mutation.apply(Mutation.java:214)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at
> org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> ~[na:1.7.0_75]
>     at
> org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
> ~[apache-cassandra-2.1.9.jar:2.1.9]
>     at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
> [apache-cassandra-2.1.9.jar:2.1.9]
>     at java.lang.Thread.run(Unknown Source) [na:1.7.0_75]
>
> Sometimes I can trigger them myself by trying to add the contents of  a
> text document that is less than 1 MB.
>
> Initially I did increase the "commitlog_segment_size_in_mb" from 32 to 64.
> Thinking to further increase it to 96.
>
> But would that be a solution to the problem? What could be possibly
> causing this?
>
> Thank you,
> George
>

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

<p dir=3D"ltr">Do you see more dropped mutation messages in nodetool tpstat=
s output.</p>
<div class=3D"gmail_quote">On Oct 6, 2015 7:51 PM, &quot;George Sigletos&qu=
ot; &lt;<a href=3D"mailto:sigletos@textkernel.nl">sigletos@textkernel.nl</a=
>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr"><div><div><div><div><div>Hello,<br><br></div>I have been frequent=
ly receiving those warnings:<br><br>java.lang.IllegalArgumentException: Mut=
ation of 35141120 bytes is too large for the maxiumum size of 33554432<br>=
=C2=A0at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:221=
) ~[apache-cassandra-2.1.9.jar:2.1.9]<br>=C2=A0=C2=A0=C2=A0 at org.apache.c=
assandra.db.Keyspace.apply(Keyspace.java:383) ~[apache-cassandra-2.1.9.jar:=
2.1.9]<br>=C2=A0=C2=A0=C2=A0 at org.apache.cassandra.db.Keyspace.apply(Keys=
pace.java:363) ~[apache-cassandra-2.1.9.jar:2.1.9]<br>=C2=A0=C2=A0=C2=A0 at=
 org.apache.cassandra.db.Mutation.apply(Mutation.java:214) ~[apache-cassand=
ra-2.1.9.jar:2.1.9]<br>=C2=A0=C2=A0=C2=A0 at org.apache.cassandra.db.Mutati=
onVerbHandler.doVerb(MutationVerbHandler.java:54) ~[apache-cassandra-2.1.9.=
jar:2.1.9]<br>=C2=A0=C2=A0=C2=A0 at org.apache.cassandra.net.MessageDeliver=
yTask.run(MessageDeliveryTask.java:64) ~[apache-cassandra-2.1.9.jar:2.1.9]<=
br>=C2=A0=C2=A0=C2=A0 at java.util.concurrent.Executors$RunnableAdapter.cal=
l(Unknown Source) ~[na:1.7.0_75]<br>=C2=A0=C2=A0=C2=A0 at org.apache.cassan=
dra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractT=
racingAwareExecutorService.java:164) ~[apache-cassandra-2.1.9.jar:2.1.9]<br=
>=C2=A0=C2=A0=C2=A0 at org.apache.cassandra.concurrent.SEPWorker.run(SEPWor=
ker.java:105) [apache-cassandra-2.1.9.jar:2.1.9]<br>=C2=A0=C2=A0=C2=A0 at j=
ava.lang.Thread.run(Unknown Source) [na:1.7.0_75]<br><br>Sometimes I can tr=
igger them myself by trying to add the contents of=C2=A0 a text document th=
at is less than 1 MB.<br><br></div>Initially I did increase the &quot;commi=
tlog_segment_size_in_mb&quot; from 32 to 64. Thinking to further increase i=
t to 96.<br></div><br>But would that be a solution to the problem? What cou=
ld be possibly causing this?<br><br></div><div></div>Thank you,<br></div>Ge=
orge<br></div>
</blockquote></div>

--089e012947843c8bbc05217161e1--