[DOCS-9982] Document that backup service will miss index builds that are performed in a rolling fashion Created: 07/Mar/17 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
|
Update https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/: If an index is built by taking a node out of the replica set, building an index on it, then putting it back into the replica set (as is our documented process for building indexes in a replica set), then there won't be an oplog entry generated for the index build. Without an oplog entry for the index build, BRS has no way to discover that that index was built. We should document this behavior, and maybe consider building a way for users to inform BRS of the new index. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |