[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: |
|
||||
| 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: |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |