For #2
There are tow mutates in thrift batch_mutate and atomic_batch_mutate. The
atomic version was just added. If you care more about the performance do
not use the atomic version..
On Sat, Apr 6, 2013 at 12:03 AM, Matt K wrote:
> Hi,
>
> I have an application that does batch (counter) writes t
Thank you Aaron and Bryan for your advice.
I have changed following parameters and now Cassandra running
absolutely fine. Please review below setting and advice am I right or
right direction.
cassandra-env.sh
#JVM_OPTS="$JVM_OPTS -ea"
MAX_HEAP_SIZE="6G"
HEAP_NEWSIZE="500M"
cassandra.yaml
hi aaron,
nodetool compactionstats on all nodes return 1 pending task :
ubuntu@app:~$ nodetool compactionstats host
pending tasks: 1
Active compaction remaining time :n/a
The command nodetool rebuild_index was launched several days ago.
2013/4/5 aaron morton
> but nothing's happening,
> If I wait 24 hours, the repair command will return an error saying that the
> node died… but the node really didn't die, I watch it the whole time.
Can you include the error, it makes it easier to know what's going on.
You should see INFO messages on the node you are running repair on that say
> We can see from below that you've tweaked and disabled many of the memory
> "safety valve" and other memory related settings.
Agree.
Also you are running with JVM heap size of 3.81GB which is non default. For a
16GB node I would expect 8GB.
Try restoring the yaml values to the defaults and
What is the IP setted in cassandra.yalm file? Try to use that IP.
2013/4/6 zg
> Hi everyone,
> I have a 3 nodes cluster, one node when I use nodetool, I met a error
> "Failed to connect to '127.0.0.1:7199':Connection timed out", use CLI and
> CQLsh is ok on this node, the other two nodes is OK
