Note that this is an implementation detail, not something that
inherently can't work with other strategies. LOCAL_QUORUM and
EACH_QUORUM are logically equivalent to QUORUM when there is a single
datacenter.
We tried briefly to add support for non-NTS strategies in
https://issues.apache.org/jira/b
Okay, great I just wanted to confirm that LOCAL_QUORUM will not work with
SimpleStrategy. There was somewhat of a debate amongst my devs that said it
should work.
Anthon
On Fri, Sep 2, 2011 at 9:55 AM, Evgeniy Ryabitskiy <
evgeniy.ryabits...@wikimart.ru> wrote:
> So.
> You have created keyspace
So.
You have created keyspace with SimpleStrategy.
If you want to use *LOCAL_QUORUM, *you should create keyspace (or change
existing) with NetworkTopologyStrategy.
I have provided CLI examples on how to do it. If you are creating keyspace
from Hector, you have to do same via Java API.
Evgeny.
Thanks Evneniy,
We encountered this exception with the following settings:
Caused by: InvalidRequestException(why:consistency level LOCAL_QUORUM not
compatible with replication strategy (org.apache.cassandra.locator
.SimpleStrategy))
at
org.apache.cassandra.t
Hi
Actually you can use LOCAL_QUORUM and EACH_QUORUM policy everywhere on
DEV/QA/Prod.
Even it would be better for integration tests to use same Consistency level
as on production.
For production with multiple DC you usually need to chouse between 2 common
solutions: Geographical Distribution or D
Okay, we are looking at setting up a production environment which means
getting our quorum settings and strategies correct. However, we need to
really understand the approach taken to get this right. So far we have been
working with co-located nodes and our prod environment is going to be
distribut
