[SERVER-14157] rs.status() shell helper reports repllag Created: 04/Jun/14 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | Needs Further Definition |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
The result returned by replSetGetStatus contains enough information to compute a "repllag" value for each member with an optime. Having the server actually perform this computation would avoid the need for it to be done (potentially poorly) client-side. Presumably the most sensible definition of repllag would be latest_optime - optime, where latest_optime is the largest optime.getTime() value of any replset member (that has an optime), but anything that is self-consistent would be fine. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 07/Mar/19 ] |
|
ping kevin.pulo |