Re: coordinator selection in remote DC

2014-11-20 Thread Tyler Hobbs
> > I did not check the code - is this snitch on by default and, maybe, used > as wrapper for configured endpoint_snitch? Yes, the dynamic snitch wraps whatever endpoint_snitch you configure, and it's on by default. > As I understand it, the dynamic snitch also has a default slight > preference

Re: coordinator selection in remote DC

2014-11-20 Thread Robert Coli
On Thu, Nov 20, 2014 at 9:03 AM, Tyler Hobbs wrote: > The difference is likely due to the DynamicEndpointSnitch (aka dynamic > snitch), which picks replicas to send messages to based on recently > observed latency and self-reported load (accounting for compactions, > repair, etc). If you want to

Re: coordinator selection in remote DC

2014-11-20 Thread Nikolai Grigoriev
Hmmm...I am using: endpoint_snitch: com.datastax.bdp.snitch.DseDelegateSnitch which is using: delegated_snitch: org.apache.cassandra.locator.PropertyFileSnitch (for this specific test cluster) I did not check the code - is this snitch on by default and, maybe, used as wrapper for configured en

Re: coordinator selection in remote DC

2014-11-20 Thread Tyler Hobbs
The difference is likely due to the DynamicEndpointSnitch (aka dynamic snitch), which picks replicas to send messages to based on recently observed latency and self-reported load (accounting for compactions, repair, etc). If you want to confirm this, you can disable the dynamic snitch by adding th

coordinator selection in remote DC

2014-11-20 Thread Nikolai Grigoriev
Hi, There is something odd I have observed when testing a configuration with two DC for the first time. I wanted to do a simple functional test to prove myself (and my pessimistic colleagues ;) ) that it works. I have a test cluster of 6 nodes, 3 in each DC, and a keyspace that is replicated as f