>
> On restart of one node 1 could see repeated errors like " Mutation of
> 22076203 bytes is too large for the maxiumum size of 16777216"
Commitlog segment size is the right lever to get C* to accept larger writes
but this is not a traditional use for cassandra. Cassandra is built to
handle lots
Thanks a ton Sebastian.
On restart of one node 1 could see repeated errors like " Mutation of
22076203 bytes is too large for the maxiumum size of 16777216"
So I increased commitlog_segment_size_in_mb from 32 to 64mb.
Followed by a rolling restart again. And now there is a single version
and
If its a tarball then root should be fine but there were some files owned
by the Cassandra user so you may want to chown those back to root.
I haven't seen your exact issue before but you have two schema versions
from your describe cluster so a rolling restart should help.
all the best,
Sebastiá
Kedar,
I recommend asking the user list user@cassandra.apache.org this list is for the
development of cassandra and you're more likely to find someone on the user
list who may have hit this issue.
Curious issue though I haven't seen that myself.
Regards,
Ryan Svihla
> On Feb 11, 2016, at 7:56
Thanks Sebastian,
Cassandra installation in our case is simply an untar.
Cassandra is started using supervisord and user as root, would you still
recommend I try using Cassandra user.
./nodetool describecluster
Cluster Information:
Name: Test Cluster
Snitch: org.apache.cassandra.loca
Keep this on. The user list, it's not appropriate for the dev list.
1) I noticed that some of your files are owned by root and others by
Cassandra. If this is a package install you should always start C* as a
service and chown your files and directories so they are owned by the
Cassandra user, not
Thanks,
kindly refer the following:
https://gist.github.com/anonymous/3dddbe728a52c07d7c52
https://gist.github.com/anonymous/302ade0875dd6410087b
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.par...@netcore.co.in
Web : www.netcore.co.in
On Thursday 1
Would you mind pasting the ouput for both nodes in gist/paste/whatever?
https://gist.github.com http://paste.debian.net
Le Jeudi 11 février 2016 11h57, kedar a écrit :
Thanks for the reply.
ls -l cassandra/data/* lists various *.db files
This problem is on both nodes.
Thanks,
Kedar Parikh
Thanks for the reply.
ls -l cassandra/data/* lists various *.db files
This problem is on both nodes.
Thanks,
Kedar Parikh
Ext : 2224
Dir : +91 22 61782224
Mob : +91 9819634734
Email : kedar.par...@netcore.co.in
Web : www.netcore.co.in
On Thursday 11 February 2016 03:57 PM, Romain Hardouin wro
What is the output on both nodes of the following command?
ls -l /var/lib/cassandra/data/system/*
If one node seems odd you can try "nodetool resetlocalschema" but the other
node must be in clean state.
Best,
Romain
Le Jeudi 11 février 2016 11h10, kedar a écrit :
I am using cqlsh 5.0.1 | Cas
10 matches
Mail list logo