Release a member slot
The server leaves the member slot and stays in Servers with its name and its mesh identity. If the server is online: when the member leads, Patroni first switches over to a healthy replica; then the console stops and disables the services on the server and deletes its PostgreSQL data and 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; until then it needs cleanup and is not free. If the cleanup cannot remove a part, the server needs cleanup too. Every other member must be healthy, and no other slot can be empty or wait for a rebuild. Then fill the slot with a server.
/api/v1/database-services/{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