One real cluster moved from DotNext under writes, and every acknowledged write is on every node #4

Merged
ferociousbyte merged 2 commits from main into stable 2026-11-16 12:12:59 +00:00

unilayer.cloud's test instance unilayer-dotnext-labs, moved by the operator while six writers wrote: 106,954 writes
acknowledged, all in all three databases once, none of the refused; the databases the same row for row afterwards.
Writes stopped for 46.3 s, most of it Kubernetes bringing the pods back and the first snapshot.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

unilayer.cloud's test instance unilayer-dotnext-labs, moved by the operator while six writers wrote: 106,954 writes acknowledged, all in all three databases once, none of the refused; the databases the same row for row afterwards. Writes stopped for 46.3 s, most of it Kubernetes bringing the pods back and the first snapshot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
unilayer.cloud's test instance unilayer-dotnext-labs, moved by the operator while six writers wrote: 106,954 writes
acknowledged, all in all three databases once, none of the refused; the databases the same row for row afterwards.
Writes stopped for 46.3 s, most of it Kubernetes bringing the pods back and the first snapshot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The test wrote one entry and then asserted at once that both followers had logged whom they follow. The write is
committed by the leader and one follower; the other may not have heard from the leader yet. CI run 18451 on 178fd41
failed on exactly that: n1, a follower, had not logged it. The check is unchanged, it now waits for the log line within
the test's patience instead of expecting it at the moment of the commit; the same for the leader's line about its
connection to the member that is stopped next. Not reproduced locally in 25 runs under CPU load.

Co-Authored-By: Claude Opus 5.5 <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!4
No description provided.