[DOCS-11480] Update reindex documentation to note that it is possible to run reindex on secondaries Created: 21/Mar/18 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: | Arnie Listhaus | 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 |
|
Our reindex documentation does not mention that it is possible to run reindex on secondaries. As currently implemented, the compact command which is used for similar reasons, places secondaries into RECOVERING mode which has the benefit of not allowing secondary reads to hit that node while the compact is running. However, the reindex command does not currently place the secondary into maintenance mode (SERVER-7824). As such, the documentation should mention as a caveat that the secondary should preferably be manually placed into maintenance mode during a reindex so that secondary reads are not impacted. |
| 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! |