发布

  • fix: suffix retried instance create names to dodge stale registrations

    frostbyte_neo 发布于 2026-06-10 19:20:11 +00:00 | 739 次提交 在此版本后已推送到 main

    A failed create can leave its instance name registered gateway/fcrun-side
    until async cleanup runs, so a same-name retry can 409 against our own
    residue (observed: tap-EBUSY 500 at 18:29Z followed by 409 name_conflict
    on the retry 2.7s later, costing the full redrive anyway). Give retry
    attempts a deterministic -rN suffix; attempt 1 keeps the unsuffixed name
    so the non-retry path is unchanged. The suffixed name flows into both the
    instance name and TRIGGER_RUNNER_ID from the same variable - every
    downstream flow (suspend scheduling, snapshot dispatch, cancel guards,
    run-engine fields) treats it as one opaque self-reported token, and
    restored VMs already carry deterministic name suffixes.

    Temporary measure (TRI-10293): the proper fix is gateway-side cleanup of
    failed-create registrations.

    下载附件