[SERVER-3575] Stuck replication condition should be made very visible Created: 11/Aug/11 Updated: 11/Jul/16 Resolved: 22/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Replication, Stability |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mathieu Poumeyrol | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | replication, rn | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
A stuck replica condition is only visible to monitoring software by checking for difference of oplog timestamp.
|
| Comments |
| Comment by Mathieu Poumeyrol [ 22/Feb/12 ] |
|
Looks good. Thanks. |
| Comment by auto [ 22/Feb/12 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: Clock skew clarifiaction |
| Comment by auto [ 22/Feb/12 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: Add lag to _replSet page |
| Comment by Kristina Chodorow (Inactive) [ 21/Nov/11 ] |
|
Adding lag to /_replSet is very do-able. > In the recent issue we had, the replica sync thread was clearly stuck. It was looping There should be an error message about it in rs.status(). I'll look into making it clearer. An acceptable-replica-lag option is a bigger request, I'd suggest making a separate feature request ticket for that if it's something you'd like to see. |