Release a DCS member slot
The server leaves the etcd member slot of a standalone DCS cluster and stays in Servers with its name and its mesh identity. If the server is online, the console stops and disables etcd on it and deletes its etcd data, and the server is free. If the server is unreachable, it leaves the slot at once, and the console deletes its data when it is online again. The other members must be healthy and keep a majority, no other slot can be empty or wait for a rebuild, and every service on the cluster must be healthy. Then fill the slot with a server.
/api/v1/dcs-clusters/{id}/slots/{member_name}/releasetse_sessionAPI key · cookierequiredidstringrequiredmember_namestringrequiredThe member name of the slot: pgnodeNN for a database service, etcdNN for a DCS cluster.
Accepted
member_namestringrequiredonlinebooleanrequiredtrue: the console stops, disables and wipes the server in the workflow. false: the server was unreachable; it leaves the slot without a wipe (at once, or on a service with a VIP when the workflow has raised the keepalived priority on the other members) and the console wipes it when it is online again.
server_idstringrequiredserver_namestringrequiredworkflow_idstringrequiredError
codestringStable code of the refusal, when the route has codes
detailsstring[]Additional detail, e.g. per-field validation failures
errorstringrequiredHuman-readable error message