Ok, so I think I found one major cause contributing to the increasing
resident size of the Cassandra process. Looking at the OpenJDK sources
was of great help in understanding the problem but my findings also
apply to the Sun/Oracle JDK because the affected code is shared by
both.
Each IncomingTcp
Hi,
We use Cassandra 0.7.4 to do TPC-C data loading on ec2 nodes. The loading
driver is written in pycassa. We test the loading speed on insert and
batch_insert, but it seems no significant difference. I know Cassandra first
write data to memory. But still confused why batch_insert does not quick
If you do CL=ONE write + CL=ALL read, then it seems OK...
You should better to stay in this thread until some of experts would
answer your question.
2011/5/14 Ryan Hadley :
> Thanks Maki,
>
> That makes sense with my symptoms... I was doing a CL=ONE for write and a
> CL=ALL for read, expecting t
Thanks Maki,
That makes sense with my symptoms... I was doing a CL=ONE for write and a
CL=ALL for read, expecting that to be sufficient.
I will try both set to ALL and see if I get better consistency.
-Ryan
On May 14, 2011, at 4:41 AM, Maki Watanabe wrote:
> It depends on what you really u
Just FYI for beginners like me: I've also write it with jython.
Getting attributes are more easier than invoke Operations. I feel
jython will be a good option to create custom monitoring/management
tools.
#!/usr/bin/jython
#
# *** This is JYTHON script. You can't run it on CPython. ***
import sys
Out of curiosity, could you try to disable mmap as well?
I had some problems here some time back and I wanted to see better what was
going on and disabled the mmap.
I actually don't think I have the same problem again, but I have seen javavm
sizes up in 30-40MB with a heap of just 16.
Haven't pa
It depends on what you really use which CL for your operations.
Your RF is 2, so if you read/write with CL=ALL, your r/w will be
always consistent. If your read is CL=ONE, you have chance to read old
data anytime, decommission is not matter. CL=QUORUM on RF=2 is
semantically identical with CL=ALL.
Typically nothing is ever logged other than the GC failures
In addition to the heapdumps,
be useful to see some GC logs
(turn on GC logs via cassandra.in.sh
Or add
-Xloggc:/var/log/cassandra/gc.log
-XX:+PrintGCDetails
)
thanks, Sri
On May 7, 2011, at 6:37 PM, Jonathan Ellis wrote:
The liv
