Acknowledge a split brain
POST/v1/protection-groups/:id/split-brain/acknowledge
Clears split_brain_risk here by saying the other region's copy is the one that was discarded and this one keeps running. Nothing else clears it but a resync: no record from the other region does, however many times it resyncs or reports. The acknowledgement takes custody here at an epoch above the other region's, and records that where the other region reads it, as a recovery here; the other region then sees a recovery above what it holds and refuses to run its own copy until it is resynced. Recorded in the audit log with who gave it and why. Operator only, and only with confirm_other_region_discarded.
Operator only: needs a system-scoped token.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 413
- 415
- 422
- 503
- default
OK
Bad Request.
invalid_request: The body is not a single JSON object, names a field this operation does not take, or gives a value of the wrong type.
Unauthorized.
unauthenticated: The token is missing, expired or not valid.
Forbidden.
forbidden: The token is not an operator token.
Not Found.
not_found: No group with this id exists.
Conflict.
split_brain_risk: The group is not in split_brain_risk, a run is acting on it, or it changed while the acknowledgement was being recorded.
Request Entity Too Large.
body_too_large: The body is larger than the service accepts.
Unsupported Media Type.
unsupported_media_type: The body is not sent as application/json.
Unprocessable Entity.
acknowledge_unconfirmed: confirm_other_region_discarded is missing or false.
Service Unavailable.
dr_not_enabled: Disaster recovery is not enabled here, or this cloud cannot write where the other region reads.
An error, as an RFC 7807 problem document.