You might want to see what quorum is configured? I meant to ask that.
*...*
*“Life should not be a journey to the grave with the intention of arriving
safely in apretty and well preserved body, but rather to skid in broadside
in a cloud of smoke,thoroughly used up, totally worn out, an
On Mar 31, 2015, at 4:59 PM, daemeon reiydelle wrote:
> What is your replication factor?
NetworkTopologyStrategy with replfactor: 2 in each DC.
Someone else asked about the endpoint snitch I'm using; it's set to
GossipingPropertyFileSnitch.
> Any idea how much data has to be processed under t
What type of snitch are you using for cassandra.yaml: endpoint_snitch ?
PropertyFileSnitch can improve performance.
- bharat
On Tue, Mar 31, 2015 at 1:59 PM, daemeon reiydelle
wrote:
> What is your replication factor?
>
> Any idea how much data has to be processed under the query?
>
> With that
On Tue, Mar 31, 2015 at 1:54 PM, Andrew Vant
wrote:
> I have a Cassandra 2.0.13 cluster with three datacenters, three nodes per
> datacenter. If I open cqlsh and do a select with any consistency level that
> crosses datacenters (e.g. QUORUM or ALL), it works, but takes 2+ minutes to
> return. The
What is your replication factor?
Any idea how much data has to be processed under the query?
With that few nodes (3) in each DC, even with replication=1, you are
probably not getting much inter-node data transfer in a local quorum, until
of course you do cross data centers and at least one full c
I have a Cassandra 2.0.13 cluster with three datacenters, three nodes per
datacenter. If I open cqlsh and do a select with any consistency level that
crosses datacenters (e.g. QUORUM or ALL), it works, but takes 2+ minutes to
return. The same statement with consistency ONE or LOCAL_QUORUM is as
