[DOCS-452] Create Best Practices for Batch Jobs (How to Manage Replica Lag) Created: 27/Aug/12  Updated: 30/Oct/23  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Barrie Segal 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:
Days since reply: 7 years, 29 weeks ago

 Description   

Often when running batch jobs, users can outrun the oplog causing secondaries to go stale. We should offer some best practices on how to avoid this, e.g. breaking up the batch into smaller jobs by periodically calling GLE.

There are already a few SERVER tickets requesting changes to be made to prevent getting RS102: SERVER-982, SERVER-3346, SERVER-4364, SERVER-4935, and SERVER-4936



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:38:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.