[M4.5] Heartbeats, leases, failover, fencing

Open
  • Is something wrong?
#227 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
distributed-systems, infrastructure

Research direction

Read ADR 0008 and SPEC 16, then inspect the control plane and agent work for M4.4; the payload does not name files or tests. Implement retry-safe certificate renewal after a lost response and validate failover with an end-to-end node-kill test: stateless apps recover on another node in under 90 seconds, while a partition test confirms stateful apps never run twice.

Written by the indexing model from the issue text.

Description

priority:P1 security-review task track:agent track:control-plane
Task id

M4.5

Track

C: control plane, A: agent

Scope
  • ADR 0008 implemented.
  • Retry-safe certificate renewal after a lost response (SPEC 16), so a lease holder is never fenced by its own renewal.
Acceptance criteria

E2E kills a node; stateless app back on another node in under 90 s; stateful app never runs twice (partition test).

Depends on

M4.4

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.