[DOCS-12542] Reclaiming space after resizing Oplog Created: 12/Mar/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 3.6
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Minor - P4
Reporter: Mark Brinsmead Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

The documented procedure to "Compact oplog.rs to reclaim disk space" might be improved on a couple points.

1. It implies, but does not make crystal-clear, that the compact operation must be performed only on SECONDARY members. I am working now with a customer who has been confused by this. (00551858)
2. The recommended step rs.stepDown() may not always work as expected in replica sets with asymmetric priorities. In a P-S-S with priorities 5, 2, and 1, when you `stepDown()` the primary, it will quickly initiate a priority-takeover, and "step back up".

Scope of changes

  • Specify in first paragraph that you must run compact against secondaries only
  • Revise rs.stepdown to specify a stepdown timeout of 120 seconds (to ensure a high-priority primary does not immediately re-elect itself)

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 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!

Generated at Thu Feb 08 08:05:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.