[SERVER-13575] Log Progress for Rollback Operations Periodically Created: 14/Apr/14 Updated: 11/Jul/16 Resolved: 30/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.10, 2.6.0 |
| Fix Version/s: | 2.7.2 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Adam Comerford | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
When doing a rollback, there is no indication of progress in the logs at all - it is difficult to determine whether the rollback is just slow or, potentially, broken. A progress indication, perhaps something like this: [log time stamp] [rsBackgroundSync] X operations processed (out of total, if known or perhaps a delta from the common point) Print this every 60 seconds to at least give evidence that something is happening. This should be visible at the default log level |
| Comments |
| Comment by Githook User [ 30/May/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: also stop double counting deletes from non-capped collections |
| Comment by Brian Goodman [ 15/Apr/14 ] |
|
It would be useful to have this status show up in an MMS view. See MMS-822. |