Hi all,
I tested Cassandra 1.1.3 version on IBM JDK 1.6 in Linux. But I got
following issue when inserting data to Cassandra.
This is the exception
ERROR {org.apache.cassandra.thrift.CustomTThreadPoolServer} - Error
occurred during processing of message.
java.lang.NullPointerException
at
org.a
Cassandra latest version ( 1.2.1) has the same issue when it runs on IBM
JDK.
NULL
1XMTHDINFO All Thread Details
NULL --
NULL
2XMFULLTHDDUMP Full thread dump J9 VM (J2RE 6.0 IBM J9 2.4 Linux amd64-64
build jvmxa6460sr5-20090519_3574320090519_035743_LHdSMr, native thr
Hello all,
I have a cluster of three nodes running 1.2.1 and I'd like to increase the
capacity by adding a new node. I'm using virtual nodes with 256 tokens and
planning to use the same configuration for the new node as well.
My cluster looks like this before adding the new node:
Status=Up/Dow
In one of the scenarios that I encountered, I needed to change the token on the
node. I added new token and started the node
with-Dcassandra.load_ring_state=false in anticipation that the node will not
pick from the locally persisted data. Is that the right way to do? or
-Dcassandra.load_ring_s
At this point I think the project should just officially state which
major and minor versions they develop and test with.
If we are using 'unsafe' all over the place it is not a surprise that
c* is not working on most JVMs.
org.apache.cassandra.utils.FastByteComparisons$LexicographicalComparerHold
At what point is it ok to move the incremental back up from the server to
offsite?Is it recommended to flush the node before doing this?
Thanks,SC
Hello,
We just hit a very odd issue in our Cassandra cluster. We are running
Cassandra 1.1.2 in a 6 node cluster. We use a replication factor of 3,
and all operations utilize LOCAL_QUORUM consistency.
We noticed a large performance hit in our application's maintenance
activities and I've b
Thank you,
Another question on this topic.
Upgrading from 1.1.2->1.1.9 requires running upgradesstables, which will
take many hours on our dataset (about 12). For this upgrade, is it
recommended that I:
1) Upgrade all the DB nodes to 1.1.9 first, then go around the ring and
run a staggered
SSTables are write once. As soon as they appear on disk they ARE
flushed. This means you can safely copy them away. You should run
nodetool snapshot first and copy those hardlinks, because this will
guarantee that the file will not be compacted away while you are
copying it.
On Sat, Feb 9, 2013 at
