deepaksharma

I am also facing the same issues using the starter 0.9.0 with Arango 3.2. A fix/resolution strategy for this would be great!

Hi @ewoutp Thank you for your reply. I understand that it is possible to remove a node when it is functioning properly. The issue arises when the the node is...

@ewoutp Thanks! I feel if the node is down, then it would be difficult to serve a request on that box (even with a force flag :O ). Please let...

Thanks! will try this and get back to you. I hade managed to dig out other endpoints from slack: curl -XDELETE :/_admin/shutdown?remove_from_cluster=1 curl :/_admin/cluster/cleanOutServer -d '{"server":"DBServer000X"}' Unfortunately the above ones...

@ewoutp That did not work for me either :(. Here is what I did: 1. Bring down a cordinator+dbserver node. 2. Started seeing node health errors for dbserver and coordinator...

Here are my findings: There are two issues which I face: a) Coordinator: Either removing the "dead" coordinator from the UI or using the removeServer endpoint, the coordinator gets removed...

@phouverneyuff This is a arangodb level issue https://github.com/arangodb/arangodb/blob/3.3/js/actions/api-cluster.js#L77 we are not getting a match on the Role(and the value returned back is role(lowercase)) which is why we are not able...