You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new keyspace id is needed every-time a new keyspace is created. PD already has an idAllocator that utilize persistent window boundary to efficiently assign new ID. It would be great if its implementation can be reused for keyspace management.
However, the current implementation of id allocator permits only one id allocator instance due to its fixed alloc path $rootPath/alloc_id and metrics label.
Currently, the single id allocator instance(server.idAllocator) was used for assigning regionID, storeID, peerID. This makes it non-ideal for allocating keyspace id, which has different bounds (1 - uint24MAX) and would preferable to be less sparse.
Therefore, parametrize id allocator's alloc path and metrics label becomes necessary.
The text was updated successfully, but these errors were encountered:
close#5294
make id allocator general purpose
Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
shhdgit
pushed a commit
to shhdgit/pd
that referenced
this issue
Jul 21, 2022
closetikv#5294
make id allocator general purpose
Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
HuSharp
pushed a commit
to HuSharp/pd
that referenced
this issue
Jul 21, 2022
closetikv#5294
make id allocator general purpose
Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Development Task
A new
keyspace id
is needed every-time a newkeyspace
is created. PD already has anidAllocator
that utilize persistent window boundary to efficiently assign new ID. It would be great if its implementation can be reused forkeyspace
management.However, the current implementation of id allocator permits only one id allocator instance due to its fixed
alloc path
$rootPath/alloc_id and metrics label.Currently, the single id allocator instance(
server.idAllocator
) was used for assigning regionID, storeID, peerID. This makes it non-ideal for allocating keyspace id, which has different bounds (1 - uint24MAX) and would preferable to be less sparse.Therefore, parametrize id allocator's alloc path and metrics label becomes necessary.
The text was updated successfully, but these errors were encountered: