reported https://issues.apache.org/jira/browse/CASSANDRA-1359
On Wed, Aug 4, 2010 at 9:51 PM, Jonathan Ellis wrote:
> That's definitely a bug.
>
> On Wed, Aug 4, 2010 at 2:13 PM, Ran Tavory wrote:
> > ok, so I don't send writes to bootstrapping or decommissioned nodes,
> that's
> > cool, but wh
That's definitely a bug.
On Wed, Aug 4, 2010 at 2:13 PM, Ran Tavory wrote:
> ok, so I don't send writes to bootstrapping or decommissioned nodes, that's
> cool, but what about the inconsistent ring view after nodetool move, isn't
> this strange?
> After the move, the moved node has the correct vi
ok, so I don't send writes to bootstrapping or decommissioned nodes, that's
cool, but what about the inconsistent ring view after nodetool move, isn't
this strange?
After the move, the moved node has the correct view of the ring but all
other nodes have the old view. I waited a few minutes after th
Don't point clients at nodes that aren't part of the ring. Cassandra
rejecting requests when you do is a "feature."
On Wed, Aug 4, 2010 at 6:52 AM, Ran Tavory wrote:
> Is this a known issue?
> Running 0.6.2 I moved a node to different token and eventually saw errors in
> the log.
>
> ERROR [ROW-
Is this a known issue?
Running 0.6.2 I moved a node to different token and eventually saw errors in
the log.
ERROR [ROW-READ-STAGE:116804] 2010-08-04 06:34:29,699
DebuggableThreadPoolExecutor.java (line 101) Error in ThreadPoolExecutor
java.lang.RuntimeException: Cannot service reads while bootst
