Ewout Prangsma

The latest starter version already has support for removing a node that does not have an agent on it. When using the `Shutdown` method (see https://github.com/arangodb-helper/arangodb/blob/master/client/api.go#L43) with `goodbye=true` the arangod...

@dashdeep13 you're correct, currently the starter can help you to remove a node when it is still alive and well. What you're talking about is a cleanup scenario after a...

@dashdeep13 You can use the following HTTP API on one of the coordinators to remove a dead server. ``` curl http[s]://coordinator-ip/_admin/cluster/removeServer -d '"SERVER_ID"' ``` You can find the `SERVER_ID` using...

@tmd313 Removing an agent is still not possible. The good news is that we're very close to merging this feature (into `arangod`) and it will be in there soon.

@dashdeep13 First of all sorry that this is taking so long. I've managed to reproduce the failure to remove a dead dbserver or coordinator from the cluster. (both using curl...

@sebastienpattyn93 for now you have 2 options: 1) Use a different IP address for the starter (the machine the starter is running on) 2) Use a different data directory We're...

Is there any more context, logs, anything?

@neunhoef @fceller please add your thoughts about this

hi @samrg472 We've not seen this error before. Can you add logs for the starter & database server (datadir//arangod.log) Also, is there anything special about your network configuration? Any specific...

Have you configured all starters with `--server.storage-engine=rocksdb` when you started them for the first time? It looks like at least one of the starters did configure mmfiles instead of rocksdb.