I'm thinking I'll have to find something similar for 2.0. I just don't
understand where the node is coming from!
Jeff
On 1 July 2015 at 10:21, Vitalii Skakun wrote:
> Hi,
>
> just a guess, there was a possibility to purge gossip state on a node, at
> least in version 1.2
>
> http://docs.datasta
Ok, I solved it. The problem was in my code. I did use FixedThreadPool in a
wrong way.
2015-07-02 15:19 GMT+02:00 Jonathan Haddad :
> If you post the code you're using to test, it would be helpful. You
> should also use cassandra-stress to see if you get similar results.
>
> On Thu, Jul 2, 2015
Hi KZ,
We're you monitoring tpstats and netstats during the bootstrap? This could
give us some more information.
Your logs look a little like 8318 but there would have to be another error
earlier in the logs and the ticket is for a node replacement not a fresh
bootstrap... Can you check for an er
Solved. Finally found that there was one node with 172.29.8.8 in gossipinfo
and appearing incomplete in status:
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host ID
Rack
UL 172.29.8.8 13.28 GB 256 9.5% null
1
Re
Is the ghost node in your system.peers on any node? Check every node (since
it's local strategy).
Otherwise the nodes must be in the endpoint list in memory and you'll have
to rolling restart. Make sure you drain though before the rolling restart
since it may be in your commit log somewhere too.
O
Hi All
Can someone please point me to where the code for bootstrapping a new node
exists?
--
Cheers
Bill
