main #7

Merged
ferociousbyte merged 2 commits from main into stable 2026-11-20 07:58:25 +00:00
No description provided.
PLAN.md loses the decision; the README and the notes say in the past tense what was measured and moved while
unilayer had both engines.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
On unilayer.cloud's cluster a restarted node reached its peers within a second and then waited 8 to 21 s for a
leader (2026-11-20, two rolling updates): the leader has to connect to it, the pod had a new address, and the
cluster's name server keeps answers for 30 s. A peer that proved who it is on a connection it made has shown where
it is, so the node connects there first, asks whoever answers for the same proof, and falls back to the name.

A follower also kept the connection to a peer that had stopped until it next sent on it, and that message, a vote
after a handover, went into the dead connection. The node now reads on the connection it sends on, which a peer
never writes to, and gives it up when it ends. Keep-alive is set so that a machine that vanished without closing
is noticed as well; that part has no test, and PLAN.md says so.

Both tests fail without the change. 292 tests pass.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
unilayer/raft!7
No description provided.