You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Brian Picciano <me...@gmail.com> on 2016/02/12 22:51:29 UTC

Can't bootstrap a node

I posted this on the IRC but wasn't able to receive any help. I have two
nodes running 3.0.3. They're in different datacenters, connected by
openvpn. When I go to bootstrap the new node it handshakes fine, but always
gets this error while transferring data:

http://gobin.io/oMll

If I follow the log's advice and run "nodetool bootstrap resume" I get the
following:

http://gobin.io/kkSu

I'm fairly confident this is not a connection issue, ping is sub-50ms, and
there isn't any packet loss that I can see. Any help would be greatly
appreciated, I'd also be happy to give any further debugging info that
might help. Thanks!

Re: Can't bootstrap a node

Posted by Alain RODRIGUEZ <ar...@gmail.com>.
Hi Brian,

Did you noticed this error: "CF 9733d050-d0ed-11e5-904a-5574a0c0fd2a was
dropped during streaming" ?

Are you dropping keyspaces or tables (old name Column Family, CF) during
the bootstrap (maybe as a client app action ?)

Or are you creating KS / CF on both DataCenters before connecting them as
described in https://issues.apache.org/jira/browse/CASSANDRA-9956 ?

Anything else that could be related (any schema changes during the
bootstrap) ?

C*heers,
-----------------
Alain Rodriguez
France

The Last Pickle
http://www.thelastpickle.com

2016-02-12 22:51 GMT+01:00 Brian Picciano <me...@gmail.com>:

> I posted this on the IRC but wasn't able to receive any help. I have two
> nodes running 3.0.3. They're in different datacenters, connected by
> openvpn. When I go to bootstrap the new node it handshakes fine, but always
> gets this error while transferring data:
>
> http://gobin.io/oMll
>
> If I follow the log's advice and run "nodetool bootstrap resume" I get the
> following:
>
> http://gobin.io/kkSu
>
> I'm fairly confident this is not a connection issue, ping is sub-50ms, and
> there isn't any packet loss that I can see. Any help would be greatly
> appreciated, I'd also be happy to give any further debugging info that
> might help. Thanks!
>