No VPN involved and no limitations, which can affects internode
communication, on network level. I'm curious why "nodetool status" shows
that all is OK and no suspicious messages in log file is such problem
exists.
I'm looking for hints how to troubleshoot such problem or maybe anyone have
seen suc
That's a good news if describecluster shows the same version on each node. Try
with a high timeout like 120 seconds to see if it works. Is there a VPN between
DCs? Is there room for improvement at the network level? TCP tuning, etc. I'm
not saying you won't have unreachable nodes but it's worth
>
> The latency is high...
>
It is but is it really causing the problem? Latency is high but constant
and not higher than ~200ms.
Regarding the ALTER, did you try to increase the timeout with "cqlsh
> --request-timeout=REQUEST_TIMEOUT"? Because the default is 10 seconds.
>
I use 25sec timeout (--r
Hi,
The latency is high...
Regarding the ALTER, did you try to increase the timeout with "cqlsh
--request-timeout=REQUEST_TIMEOUT"? Because the default is 10 seconds. Apart
the unreachable nodes, do you know if all nodes have the same schema version?
Best,
Romain
I had to face this too, but precisely the "unsafeAssassinateEndpoint"
removed the "UNREACHABLE" nodes (from describe cluster - CLI). After that,
I had these ghost host marked as "STATUS:LEFT" on gossipinfo (nodetool) and
my truncate could run properly. But this is only my own experience, and you
mi
Have to disagree with the "does no harm" comment just a tiny bit. I had a
similar situation recently and coincidentally needed to do a CF truncate.
The system rejected the request saying that not all nodes were up.
Nodetool ring said everyone was up but nodetool gossipinfo said there were
vestig
Hello,
Thanks for your fast response. That makes sense. I'll just keep an eye on
it then.
Many thanks,
Vasilis
On Wed, May 22, 2013 at 10:54 AM, Alain RODRIGUEZ wrote:
> Hi.
>
> I think that the "unsafeAssassinateEndpoint" was the good solution here. I
> was going to lead you to this solution
Hi.
I think that the "unsafeAssassinateEndpoint" was the good solution here. I
was going to lead you to this solution after reading the first part of your
message.
"Does anyone know why the dead nodes still appear when we run "nodetool
gossipinfo" but they don't when we run "describe cluster" fro
