Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PG Move destroy all data blocks #477

Open
sanebay opened this issue Jul 31, 2024 · 1 comment
Open

PG Move destroy all data blocks #477

sanebay opened this issue Jul 31, 2024 · 1 comment
Assignees
@Hooper9973
Labels
PG Move Replication
Milestone
MileStone4.3

Comments

@sanebay
Copy link
Contributor

sanebay commented Jul 31, 2024

Make sure same chunk is not allocated to multiple PG's. Delete data when a PG is removed. Free up all blks by traversing index in batch or find all chunks used by PG and free them in one shot. Latter option is better if chunks are not shared across PG.
@sanebay sanebay self-assigned this Jul 31, 2024
@sanebay sanebay added this to the MileStone4.4 milestone Jul 31, 2024
@sanebay sanebay modified the milestones: MileStone4.4, MileStone4.3 Aug 8, 2024
@xiaoxichen xiaoxichen modified the milestones: MileStone4.3, MileStone4.4 Aug 14, 2024
@sanebay sanebay modified the milestones: MileStone4.4, MileStone4.3 Aug 15, 2024
@sanebay sanebay removed their assignment Aug 15, 2024
@JacksonYao287
Copy link
Contributor

this will be done in eBay/HomeObject#231

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Hooper9973 Hooper9973

Labels
PG Move Replication
Projects
None yet
Milestone
MileStone4.3
Development

No branches or pull requests
4 participants
@xiaoxichen @Hooper9973 @JacksonYao287 @sanebay