[SERVER-38323] Create an index builds interface for the embedded version of the server Created: 29/Nov/18  Updated: 29/Oct/23  Resolved: 06/Dec/18

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-38396 Improve the IndexBuildsCoordinator un... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-12-03, Storage NYC 2018-12-17
Participants:
Story Points: 5

 Description   

The IndexBuildsCoordinator is for managing index builds across a replica set. It links in networking and has a ThreadPool on which to run index builds.

The embedded server cannot link to networking code, nor can it use ThreadPools. Therefore, we must make a simple class that builds indexes via the IndexBuildsManager. There is no need for asynchronous threads on an embedded server, which is effectively a standalone without networking or asynchronously running threads.

I haven't looked into whether it is possible to just make a separate class to link into embedded, or inheritance is necessary, necessitating splitting the existing IndexBuildsCoordinator into and interface and implementation. I'd guess inheritance is necessary, since commands in the standalone library are probably all included in the greater repl inclusive libraries? Shims are also a potential tool, I haven't explored that idea, either.



 Comments   
Comment by Githook User [ 06/Dec/18 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com', 'username': 'DiannaHohensee'}

Message: SERVER-38323 turn the IndexBuildsCoordinator into an interface and add an implementation for embedded
Branch: master
https://github.com/mongodb/mongo/commit/e9030987ff429ea3d80f30bf7e857caef86bc2ae

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