Repository navigation
feat(cluster)!: add per-topic replication factor - #4692
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4692 +/- ##
=============================================
- Coverage 90.91% 80.74% -10.18%
- Complexity 3857 3860 +3
=============================================
Files 1551 1555 +4
Lines 395231 400900 +5669
Branches 329371 334848 +5477
=============================================
- Hits 359336 323701 -35635
- Misses 28672 69907 +41235
- Partials 7223 7292 +69
🚀 New features to boost your workflow:
|
spetz
left a comment
There was a problem hiding this comment.
Outside this diff and also on master: a replaced member of a group with three or more members rejoins with an empty log as Init, because its initialization record went with the disk and build_partition_fresh decides restarted = replica_count > 1 && !first_initialization (core/server/src/partition_helpers.rs:998, the same line at the merge base). It starts Normal and votes in view changes, since only Status::Recovering is barred (core/consensus/src/impls.rs:3906, core/consensus/src/impls.rs:4113). With three members both quorums are 2, so once the primary fails, the wiped member and a member that lagged can complete a view change without an op that the primary and the wiped member committed, and the new view drops it. The comment above core/server/src/partition_helpers.rs:269 already says that an Init join is safe only for a replica that never served the group.
Closes #4663