avoid writing blocks to draining nodes ? #815
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#815
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Currently, when nodes are being removed from the layout, they continue receiving writes for metadata as per the consistency protocol. This means also that they will continue receiving the block_ref entries and the data blocks for the partitions they were responsible of. This is an issue as it can cause nodes to fill up quickly, which is especially problematic when we are removing nodes that are full to replace them with bigger nodes. We should probably find a way to avoid storing blocks on draining nodes, as long as we have a quorum of writes on other nodes.