Hello Everybody,
I am trying to merge two clusters into a single cluster ( the rationale being
easier administration apart from better load balancing etc)
The plan is to rename a cluster (QAPERF1) as the same name as the second
cluster (QAPERF2). Then alter the cassandra-toppology.properties an
3 node
cent os
CPU 8core memory 32GB
cassandra 1.2.5
my scenario: many counter incr, every node has one client program, performance
is 400 wps /every clicent (it’s so slowly)
my question：
Ø nodetool tpstats
-
Pool NameActive Pending Com
Hi All,
We are running a 1.0.9 cluster with 3 nodes (RF=3) serving a load of
approximately 600GB, and since I am fairly new to Cassandra, I'd like to
compare notes with other people running a cluster of similar size (perhaps
not in the amount of data, but the number of nodes).
Does anyone have CP
Hi Jabbar,
I was able to get the performance issue resolved by reusing the connection
object. It will be interesting to see what happens when I use a connection pool
from a app server.
I still think it would be a good idea to have a minimal mode for metadata. It
is rare I use metadata.
Re
Looks like the cause of the error was because of not specifying num_tokens in
the cassandra.yaml file. I was under the impression that setting a value of
num_tokens will override the initial_token value . Looks like we need to set
num_tokens to 1 to get around this error. Not specifying anythin
