Zero has an endpoint to remove nodes - that was it I mentioned
/removeNode?id=3&group=2
More about Dgraph Zero - Deploy
Yes I know. The same removeNode do ratel as i was looking in logs
Cuz you need to remove the unwanted node from the RAFT context. It will keep trying to connect until you remove it.
removeNode should remove from RAFT context as I understand?
If this was a leader you should first move its tablets(predicates, indexes) to another group before removing it.
I did. I repeated everything on clean cluster. Created HA cluster(RF 3). Then added one new node. No date in this new group.
"2": {
"members": {
"4": {
"id": "4",
"groupId": 2,
"addr": "alpha4:7080",
"leader": true,
"amDead": false,
"lastUpdate": "1680590254",
"learner": false,
"clusterInfoOnly": false,
"forceGroupId": false
}
},
"tablets": {},
"snapshotTs": "0",
"checksum": "0",
"checkpointTs": "0"
}
},
Then shot removeNode
curl "localhost:6081/removeNode?id=4&group=2"
Removed node with group: 2, idx: 4
And the same problem as i described above. Group 2 remain spam in logs etc.
It looks like there should be endpoint like remove[Empty]Group
Just tried do cluster backup and as expected ended with
E0404 07:10:04.874895 15 backup_ee.go:209] Error received during backup: Couldn't find a server in group 2
E0404 07:10:04.874951 15 queue.go:237] task 0x108256006: failed: Couldn't find a server in group 2