[SERVER-76554] Handle bucket _ids collision during chunk migration for a sharded time-series collection Created: 26/Apr/23  Updated: 04/May/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Arun Banala Assignee: Backlog - Query Integration
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Query Integration
Operating System: ALL
Participants:

 Description   

We migrate the whole buckets during chunk migration, so the chance of collision is higher for time-series collection since we prefix the first 4 bytes of _id with timestamp. So there are fewer bytes to generate a unique id across the cluster.

We can consider a workaround to regenerate the bucket (with a new _id) when a chunk migration for time-series collection fails because of _id collision


Generated at Thu Feb 08 06:32:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.