Work on the partition assignation algorithm #266
No reviewers
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#266
Loading…
Reference in New Issue
No description provided.
Delete Branch "bug/layout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Initially, this PR proposes a small change that helps ensure that nodes for each partition are spread over all datacenters, a property that wasn't ensured previously when going from a 2 DC deployment to a 3 DC deployment. That code was used to fix Deuxfleurs' production cluster which had this exact issue. However, the whole partition assignation algorithm is wanky and needs deep thought to be fixed.
73e891cf5c
toa74b6baa3b
a74b6baa3b
to509d256c58
We will probably soon have an algorithm with a perfect optimization solution for the partition assignation problem. In the meantime, this PR helps the current algorithm better equilibrate the number of partitions assigned to nodes within a zone.
WIP: Work on the partition assignation algorithmto Work on the partition assignation algorithm