Skip to content

[checkpoint] Declare and test LongMT restart-only actor pools #3296

Closed as not planned

Description

@ananthsub

Parent

Child of #3223 and #3024.

Shared state

resources_servers/longmt_eval/app.py owns a lazily initialized SegALE/Ray evaluator actor pool, initialization flag, lock, and reconstructible caches rather than per-rollout semantic state.

Proposed capability

Advertise restart-only dependency recreation, rebuild and health-check actors before resume, and keep in-flight verification outside a published checkpoint.

Do not serialize futures, locks, credentials, waiters, or raw external handles. Capability reporting must distinguish coordinated-global, drain-only, and restart-only semantics from ordinary per-session export/restore.

Acceptance criteria

  • Equivalent verification succeeds after cold actor recreation; stale actor references and initialization failure surface clearly without claiming export/restore.
  • Prepare accounts for every accepted shared operation and fails closed at its deadline.
  • Process replacement leaves no stale waiter, batch member, metric interval, or actor reference.
  • Duplicate prepare/restore/resume is idempotent or rejected deterministically.
  • Cold restart and failure cleanup are covered.

Activity

  1. added
    featureNew capabilities, enhancements, or enablement work
    area:environmentIndividual environments, benchmarks, verifiers, and environment-specific resources servers
    on Sep 10, 2026
  2. ananthsub commented on Oct 13, 2026

    @ananthsub
    ContributorAuthor

    Superseded by the partial-rollout checkpointing design in #3882 onward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:environmentIndividual environments, benchmarks, verifiers, and environment-specific resources serversfeatureNew capabilities, enhancements, or enablement work

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions