Skip to content

Conversation

@neunhoef
Copy link
Member

@neunhoef neunhoef commented Mar 12, 2019

@ghost ghost assigned Simran-B Mar 12, 2019
@ghost ghost added the 2 - Working label Mar 12, 2019
….com/arangodb/kube-arangodb into documentation/drain-mandatory-cleanout
@ghost ghost assigned neunhoef Mar 12, 2019
@Simran-B
Copy link
Contributor

What is this sentence supposed to say?

(please compare the above output of the /_admin/cluster/health API).

compare above output to the output of ... ?

Does the format follow the one of the cluster health API, or should the user check if both report the same things?

@sleto-it
Copy link
Contributor

sleto-it commented Mar 18, 2019

@Simran-B to reply to your question:

I believe here we are asking the following:

  • we are asking to call /_admin/cluster/cleanOutServer, and we have to pass to this call a json document with the name of the dbserver to be clened-out . In our example {"server":"DBServer0006"}

  • "(please compare the above output of the /_admin/cluster/health API)" I believe means the following: we are saying to the user that this "DBServer0006" is not a name we invented - it is the one we get as "ShortName" of DBserver from the /_admin/cluster/health

I believe this was the meaning - please could you reward and make it more clear?
Does this answer? so we merge and publish

thanks

@Simran-B Simran-B merged commit 013c3ae into master Mar 19, 2019
@ghost ghost removed the 2 - Working label Mar 19, 2019
@informalict informalict deleted the documentation/drain-mandatory-cleanout branch November 7, 2019 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants