I manually removed entries from System.peers.
The improvements can well be coincidental as various other apps were also
running on the same test bed.
On Tue, Apr 1, 2014 at 8:43 PM, Sylvain Lebresne wrote:
> What does "Did that" mean? Does that means "I upgraded to 2.0.6", or does
> that mean "
What does "Did that" mean? Does that means "I upgraded to 2.0.6", or does
that mean "I manually removed entries from System.peers". If the latter,
I'd need more info on what you did exactly, what your peers table looked
like before and how they look like now: there is no reason deleting the
peers e
Did that and I actually see a significant reduction in write latency.
On Tue, Apr 1, 2014 at 5:35 PM, Sylvain Lebresne wrote:
> On Tue, Apr 1, 2014 at 1:49 PM, Apoorva Gaurav
> wrote:
>
>> Hello Sylvian,
>>
>> Queried system.peers on three live nodes and host4 is appearing on two of
>> these.
>
On Tue, Apr 1, 2014 at 1:49 PM, Apoorva Gaurav wrote:
> Hello Sylvian,
>
> Queried system.peers on three live nodes and host4 is appearing on two of
> these.
>
That's why the driver thinks they are still there. You're most probably
running into https://issues.apache.org/jira/browse/CASSANDRA-6053
Hello Sylvian,
Queried system.peers on three live nodes and host4 is appearing on two of
these.
On Tue, Apr 1, 2014 at 5:06 PM, Sylvain Lebresne wrote:
> On Tue, Apr 1, 2014 at 12:50 PM, Apoorva Gaurav > wrote:
>
>> Hello All,
>>
>> We had a 4 node cassandra 2.0.4 cluster ( lets call them hos
On Tue, Apr 1, 2014 at 12:50 PM, Apoorva Gaurav
wrote:
> Hello All,
>
> We had a 4 node cassandra 2.0.4 cluster ( lets call them host1, host2,
> host3 and host4), out of which we've removed one node (host4) using
> nodetool removenode command. Now using nodetool status or nodetool ring we
> no lo
Hello All,
We had a 4 node cassandra 2.0.4 cluster ( lets call them host1, host2,
host3 and host4), out of which we've removed one node (host4) using
nodetool removenode command. Now using nodetool status or nodetool ring we
no longer see host4. It's also not appearing in Datastax opscenter. But
