Thanks Sebastian, a restart solved the problem!
On Wed, Oct 14, 2015 at 3:46 PM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> We still keep endpoints in memory. Not sure how you git to this state but
> try a rolling restart.
> On Oct 14, 2015 9:43 AM, "Tom van den Berge"
Check system.peers table to see if the IP is still there. If so edit the
table and remove the offending IP.
You are probably running into this:
https://issues.apache.org/jira/browse/CASSANDRA-6053
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian |
Remember that the system keyspace uses LocalStrategy: each node has its own
set of system tables. -ml
On Wed, Oct 14, 2015 at 9:17 AM, Tom van den Berge <
tom.vandenbe...@gmail.com> wrote:
> Hi Carlos,
>
> I'm using 2.1.6. The mysterious node is not in the peers table. Any other
> ideas?
> One
Thanks for that Michael, I did not know that. However, the node is not
listed in the system.peers table on any node, so it seems that the problem
is not in this table.
On Wed, Oct 14, 2015 at 3:30 PM, Laing, Michael
wrote:
> Remember that the system keyspace uses
We still keep endpoints in memory. Not sure how you git to this state but
try a rolling restart.
On Oct 14, 2015 9:43 AM, "Tom van den Berge"
wrote:
> Thanks for that Michael, I did not know that. However, the node is not
> listed in the system.peers table on any node,
Hi Carlos,
I'm using 2.1.6. The mysterious node is not in the peers table. Any other
ideas?
One of my existing nodes is not present in the system.peers table, though.
Should I be worried?
Regards,
Tom
On Wed, Oct 14, 2015 at 2:27 PM, Carlos Rolo wrote:
> Check system.peers