droboticflow/docs/drosync/conflicts-runbook.md
2026-07-28 20:43:46 +08:00

29 lines
1.9 KiB
Markdown

# Conflict runbook
## Normal conflict
A target conditional commit returning HTTP 412 is not data loss. The coordinator leaves the original key unchanged and conditionally creates:
`{original}.__conflict__{UTC}_{shortItemId}`
The suffix contains no user identity. Mongo records the logical target, physical conflict key, session, item, actor, expected base, and committed remote version.
## Administrator force overwrite
Force overwrite is disabled by default. It can only be enabled after the space is `update_enabled`, the administrator has confirmed exclusive ownership of the prefix, and `allowForceOverwrite` is explicitly set. The action creates a separate immutable operation item, copies from the preserved conflict object to the logical target with a fresh conditional ETag check, and keeps the conflict object. A concurrent write returns a precondition failure and must be reviewed again; it never degrades to an unconditional overwrite.
## Operator procedure
1. Open `/object-sync` → Conflicts and identify the session/item.
2. Compare the original and conflict object using recorded SHA-256, size, source mtime, ETag, and versionId. Do not interpret multipart ETag as SHA-256.
3. Decide outside drosync which business object should become canonical.
4. If a manual BOS operation is required, record the change ticket and then run space reconciliation.
5. Keep the space disabled if reconciliation reports drift. Re-run capability probe only on its dedicated temporary key.
6. Re-enable create or update only after the gate is again satisfied.
Conflicts are never deleted automatically. Session abort and rollout rollback also do not delete them.
## Lease incident
Force release only after verifying the owning daemon is stopped or its credential is revoked. The permanent fencing counter remains and increments on the next acquire; releasing a lease cannot validate an older token.