[SERVER-40261] Remove special no-collection-uuid handling in IndexBuildsCoordinator::startIndexRebuildForRecovery Created: 21/Mar/19  Updated: 27/Oct/23  Resolved: 23/Jun/20

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-40126 Catch MustDowngrade errors thrown by ... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

With the completion of SERVER-40126, we should now be able to safely throw a MustDowngrade error in IndexBuildsCoordinator::startIndexRebuildForRecovery, instead of working around not having a collection UUID.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 23/Jun/20 ]

I think this has gone away. This was the relevant code back in v4.2. I don't see any UUID generation in the index builder code today.

Generated at Thu Feb 08 04:54:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.