Azure / Azure/elastic-db-tools

SMM: Easy way to 'defrag' shard map by merging adjacent fragmented ranges

Open
#85 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
147
Forks
108
PR merge metrics
No merged PRs in 30d

Description

After using the Split-Merge tool multiple times to move around shard ranges, it's possible to end up with a highly 'fragmented' shard map that has several contiguous ranges mapped to the same shard. e.g. in the below layout, the mappings to Shard 2 are 'fragmented' and could potentially be merged into a single mapping. On a large scale this may cause perf and usability issues.

[0, 10) --> Shard 1
[10, 11) --> Shard 2
[11, 12) --> Shard 2
[12, 13) --> Shard 2
[13, 14) --> Shard 2
[14, 15) --> Shard 2
[15, 20) --> Shard 3

It would be nice to have a simple way to automatically detect and merge these mappings.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.