Carlos, so you essentially replace the 33 node. Did you follow this https://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_replace_node_t.html? The link is for 2.x not sure about 3.x. What if you change the new node to .34?
On Mon, Jan 11, 2016 at 12:57 AM, Carlos A <nando....@gmail.com> wrote: > Hello all, > > I have a small dev environment with 4 machines. One of them, I had it > removed (.33) from the cluster because I wanted to upgrade its HD to a SSD. > I then reinstalled it and tried to join. It is on UJ status for a week now > and no changes. > > I had tried node-repair etc but nothing. > > nodetool status output > > Datacenter: DC1 > =============== > Status=Up/Down > |/ State=Normal/Leaving/Joining/Moving > -- Address Load Tokens Owns Host ID > Rack > UN 192.168.1.30 16.13 MB 256 ? > 0e524b1c-b254-45d0-98ee-63b8f34a8531 RAC1 > UN 192.168.1.31 20.12 MB 256 ? > 1f8000f5-026c-42c7-8189-cf19fbede566 RAC1 > UN 192.168.1.32 17.73 MB 256 ? > 7b06f9e9-7c41-4364-ab18-f6976fd359e4 RAC1 > UJ 192.168.1.33 877.6 KB 256 ? > 7a1507b5-198e-4a3a-a9fd-7af9e588fde2 RAC1 > > Note: Non-system keyspaces don't have the same replication settings, > effective ownership information is meaningless > > Any tips on fixing this? > > Thanks, > > C. >
