[SERVER-6828] At high log verbosity, log all ops as they are applied on a secondary Created: 22/Aug/12 Updated: 11/Jul/16 Resolved: 05/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Perhaps at level -vvv |
| Comments |
| Comment by auto [ 05/Nov/12 ] |
|
Author: {u'date': u'2012-11-05T21:13:28Z', u'email': u'rassi@10gen.com', u'name': u'Jason Rassi'}Message: |
| Comment by J Rassi [ 05/Nov/12 ] |
|
After discussion with milkie, we decided that the functionality already present (the sync thread's "replication batch size" boundary message, and the workers' "applying op" messages) is sufficient. The resolution for this issue will be to change the log level for the "applying op" message from 6 to 3. |
| Comment by Eric Milkie [ 28/Sep/12 ] |
|
Note that right now we do log (at level 6!) when we add ops to the oplog (see oplog.cpp:732), but this will not show ops as they are applied to data. |