scheduler_conflict: Another scheduler holds this database

Each database has exactly one scheduler. Another live process already holds the scheduler lease for it, so this deployment refuses to start: it logs the message (which names the lease holder and when the lease ends), shuts down and exits. Nothing was served.

What to do

On the wire

No route answers this code in this release: it is a start-up refusal, seen in the deployment's log, not in an HTTP response.

If a route ever passed it on, it would take the owner-api's state shape: HTTP 409, error type state_error. With Dynamo-Error-Detail: 1:

{
  "error": "state",
  "detail": "…",
  "errorDetail": {
    "type": "state_error",
    "code": "scheduler_conflict",
    "message": "…",
    "param": null,
    "doc_url": "…/errors/scheduler_conflict.md",
    "fix": "another scheduler holds this database; stop it first"
  }
}

See all error codes.