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
Currently, when a shard is deleted, it is simply marked with a timestamp in the DeletedAt field.
For long running instances, this can cause a build up of shard infos in the data store that create unnecessary garbage when being cloned as well as unnecessary cycles during searches of the shards.
Proposal
Each data node that successfully drops the shard will remove itself from the owner group of the shard.
A periodic service that runs every 30 minutes will prune all shards from the meta store that have no owners, or the DeletedAt is more than 2 weeks old.
The text was updated successfully, but these errors were encountered:
Problem Statement
Currently, when a shard is deleted, it is simply marked with a timestamp in the
DeletedAt
field.For long running instances, this can cause a build up of shard infos in the data store that create unnecessary garbage when being cloned as well as unnecessary cycles during searches of the shards.
Proposal
prune
all shards from the meta store that have no owners, or theDeletedAt
is more than 2 weeks old.The text was updated successfully, but these errors were encountered: