Hmm, interesting. You're right that it's a bug; those two are
supposed to be equivalent.
On Thu, Dec 30, 2010 at 4:02 PM, Thor Carpenter
wrote:
> So, I found a solution, but I think there is a (trivial) bug.
>
> The broken keyspace:
>
> create keyspace KeyspaceDC1 with
> replication_factor =
So, I found a solution, but I think there is a (trivial) bug.
The broken keyspace:
create keyspace KeyspaceDC1 with
replication_factor = 1 and
placement_strategy = 'org.apache.cassandra.locator.NetworkTopologyStrategy'
and
strategy_options = [{DC1:1, DC2:0}];
The fixed keyspace:
cr
In an attempt to replicate this error on a simpler system I have come across a
different error but seemingly related problem. Now I am getting the following
exception in system.log.
DEBUG [pool-1-thread-3] 2010-12-29 12:10:38,897 CassandraServer.java (line 362)
insert
ERROR [pool-1-thread-3] 2
OK, attached are the logs.
At time 15:55 I performed a write with CL = ONE, a subsequent read with CL =
ONE and received correct results. Similar results occur with any read CL other
than LOCAL_QUORUM.
At time 15:58 I performed a write with CL = ONE, a subsequent read with CL =
LOCAL_QUORUM
Turn on debug logging to see what nodes the request gets sent to, and
which ones replied.
[dev to BCC]
On Tue, Dec 28, 2010 at 1:59 PM, Thor Carpenter
wrote:
> Hi All,
>
> I am a bit stumped. When reading at a CL of local_quorum I get
> TimedOutExceptions however when reading at any other CL,
