[SERVER-9046] Secondaries that perform (foreground) index builds should not be considered for reads with secondaryPreferred Created: 21/Mar/13  Updated: 10/Dec/14  Resolved: 21/Mar/13

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

Type: Improvement Priority: Major - P3
Reporter: Thomas Rueckstiess Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:

 Description   

When a secondary builds an index, it is currently built in the foreground. SecondaryPreferred will still consider this node to be healthy, however the read blocks until the index is complete.

This should be changed so that this node is not considered a valid target for a secondaryPreferred reads anymore until the index build is complete.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 21/Mar/13 ]

foreground index builds are design to block, and as such do not think this makes sense.

making background indexes actually background on secondaries is important, and is this case: SERVER-2771

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