[SERVER-982] replication: warn if significant percentage of the oplog is in use Created: 07/Apr/10 Updated: 06/Dec/22 Resolved: 08/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Trivial - P5 |
| Reporter: | Dwight Merriman | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
we should warn people, at least in the log file, if they are using a significant % of their oplog. say more than a third. then they might notice and be able to increase it before their slaves are dead. this would be good in various montioring tools too, % of oplog in use. perhaps could be shown in serverStatus() |
| Comments |
| Comment by Dwight Merriman [ 16/Jul/11 ] |
|
right. the former. |
| Comment by Scott Hernandez (Inactive) [ 16/Jul/11 ] |
|
Dwight, I assume you mean if secondaries are pull from more than a 1/3 of the way down the oplog? Another way to look at this is how much of the oplog is being kept in memory, but that only makes sense if memory < data-size. |