[SERVER-13304] starting background index builds on secondaries needs to be synchronous Created: 21/Mar/14  Updated: 04/Feb/15  Resolved: 06/Jan/15

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: 2.6.0-rc2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16274 secondary fasserts trying to replicat... Closed
Related
related to SERVER-13305 fix batch_write_command_insert for sm... Closed
Operating System: ALL
Participants:

 Description   

When a background index build op comes down the replication op stream, the op-application thread spawns a new thread and lets it run. We depend on being able to detect that the bg index build is running for proper operation of other commands that may be subsequently applied by the replication system (such as drop collection).
There is a race between when the thread is created and when the thread first becomes detectable as a bg index build by other commands. We need this to be synchronous (or come up with a new design).
In order to hit this bug, you would need to run one of the index-affecting commands immediately after a background index build completed on a primary. The effect might be that you would get a collection on the secondary that didn't exist on the primary, or that a collection would not have an index on the secondary that did on the primary.


Generated at Thu Feb 08 03:31:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.