[SERVER-4348] Need uptime for cluster Created: 22/Nov/11 Updated: 06/Dec/22 Resolved: 22/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Sridhar Nanjundeswaran | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
Currently rs.status shows the indiv uptimes for each of the nodes in the cluster. Need a method to query for how long the cluster has been active (atleast one node). |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 22/Nov/11 ] |
|
This would imply that each primary passes on the "replica set uptime" to the next primary. This is simply not a concept which exists now nor would I expect it to be worth the overhead. Should it count the total time any replica is running from the time that a primary exists in order to calculate the total "uptime" of the replica set? If so, should it count the "downtime" during ths election as the time which the replica set could have been up? Would it only require a primary, or would any replica (secondary) count? |