Re: Configuring the keyspace correctly - NTS

2011-09-14 Thread Anthony Ikeda
Aaron, when using the RackInferringSnitch, is the octet correlated from the rpc_address or listen_address? I just noticed that when I tried to configure this locally on my laptop I had to "0" (127.0.0.1) instead of "160" (192.160.202.235) Anthony On Wed, Sep 14, 2011 at 3:15 PM, aaron morton wro

Re: Configuring the keyspace correctly - NTS

2011-09-14 Thread Anthony Ikeda
Great that makes perfect sense - I apologise for not getting this right it seems I'm doing someone elses job here. Anthony On Wed, Sep 14, 2011 at 3:15 PM, aaron morton wrote: > The strategy_options for NTS accept the data centre name and the rf, > [{ : }] > > Where the DC name comes from the s

Re: Configuring the keyspace correctly - NTS

2011-09-14 Thread aaron morton
The strategy_options for NTS accept the data centre name and the rf, [{ : }] Where the DC name comes from the snitch, so… SimpleSnitch (gotta love this guy, in there day in day out putting in the hard yards) puts all the nodes in "datacenter1" which is why thats in the defaults. RackInferring

Configuring the keyspace correctly - NTS

2011-09-14 Thread Anthony Ikeda
Okay, in a previous post, it was stated that I could use a NetworkTopologyStrategy in a singel data centre by setting up my keyspace with: create keyspace KeyspaceDEV with placement_strategy = 'org.apache.cassandra.locator.NetworkTopologyStrategy' and strategy_options=[{datacenter1:3}];