We're using Cassandra 1.1 with Hector 1.1 library. We've found that reducing
the CL when an exception occurs is useful as it's usually easier to deal with
things not being consistent for a few seconds than the database read/write not
succeeding at all.
We have multiple DCs and use NetworkTopolo
Using PropertyFileSnitch you can fine tune the topology of the cluster.
What you tell Cassandra about your "DC" and "rack" doesn't have to match how
they are in real life. You can create virtual DCs for Cassandra and even treat
each node as a separate rack.
For example, in cassandra-topology.p
is responsible for, data is
still read and write there. It just won't be replicated since replication
factor is not defined.
Bill
On Thu, Apr 19, 2012 at 1:18 PM, Richard Lowe
mailto:richard.l...@arkivum.com>> wrote:
Yes it is possible. Put the following as the last line of your
Yes it is possible. Put the following as the last line of your topology file:
default=unknown:unknown
So long as you don't have any DC or rack with this name your local node will
not be able to address any nodes that aren't explicitly given in its topology
file.
However bear in mind that, whil
I'd double-check the firewall on each node to make sure the storage and RPC
ports aren't being blocked.
We've found that "Up" in nodetool ring output reflects the gossip status, which
means only that one of the nodes can contact the node, not necessarily the
entire ring. It's possible for the e
