[SERVER-49215] Differentiate internal idents used for resumable index build information from other internal idents Created: 30/Jun/20  Updated: 29/Oct/23  Resolved: 10/Sep/20

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

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-43988 shutdown ({force:false}) should refus... Closed
is related to SERVER-47155 Limit the number of simultaneous inde... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-09-21
Participants:

 Description   

During startup recovery, we should be able to identify the relevant internal idents for resuming index builds. However, right now there isn't a way to differentiate internal idents used for resumable index builds from other internal idents without looking at their contents.

One possible idea is to add a filename prefix to internal idents specific to resumable index builds.



 Comments   
Comment by Githook User [ 11/Sep/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-49215 Differentiate internal idents used for resumable index build information from other internal idents
Branch: svilen-optimizer-poc
https://github.com/mongodb/mongo/commit/b68df4e87d60fcaeb5cb5ea34762695910c8f2c6

Comment by Githook User [ 10/Sep/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-49215 Differentiate internal idents used for resumable index build information from other internal idents
Branch: master
https://github.com/mongodb/mongo/commit/b68df4e87d60fcaeb5cb5ea34762695910c8f2c6

Comment by Benety Goh [ 27/Aug/20 ]

The number of internal idents containing resumable build information that may be written on shutdown is bounded by the number of active index builds. Starting in SERVER-47155, the number of index builds that may be started by users on a primary is limited by the maxNumActiveUserIndexBuilds server parameter (current default is 3).

In addition, SERVER-43988 makes it less likely that the server will shut down with active index builds without an override.

Generated at Thu Feb 08 05:19:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.