8000 cron: automatic owner failover when the owner is unavailable · Issue #117 · acidtib/jiji · GitHub
[go: up one dir, main page]

Skip to content

cron: automatic owner failover when the owner is unavailable #117

Open

Description

@acidtib

Summary

Cron ownership only moves when the CLI reconciles (after deploy, restart, rollback, or scale). If the owner's host goes down, its jobs stop running until someone redeploys. Specs are agent-local and never replicated, so no other agent knows to take over. This is a feature addition: the website documents "Owner failover is not automatic."

Scope

  • Automatic owner failover when the current owner is unavailable.
  • Needs a design for who decides (agents via the replicated catalog vs. the CLI), how a new owner gets the spec without replication, and how double runs are avoided when the old owner comes back (fencing).

Done when

The cron reference on the website ("Ownership" and "Current Limits") and AGENTS.md are updated in the same change.

Code: crates/jiji-cli/src/cron_reconcile.rs, crates/jiji-agent/src/cron.rs, crates/jiji-agent/src/scheduler.rs.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0