[SERVER-42023] Log the oplog entry when it get applied to the initial syncing node Created: 01/Jul/19 Updated: 06/Dec/22 Resolved: 01/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vlad Rachev (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
TIG-1504 will emphasis when an operation is being executed by the primary, but it's hard to tell when that operation gets applied to the initial syncing node. This would be helpful for future debugging. The log can be added for log level 4. |
| Comments |
| Comment by Judah Schvimer [ 01/Jul/19 ] |
|
Can I close this as "Won't Fix"? |
| Comment by Judah Schvimer [ 01/Jul/19 ] |
|
I think that is fine. If it seems to be generating too much logging, we can give it its own log component. |
| Comment by Vlad Rachev (Inactive) [ 01/Jul/19 ] |
|
judah.schvimer yes they seem sufficient. I did not notice them because the fuzzer doesn't run with [repl: 3] log verbosity. Can we run the fuzzer with that log level, or will it introduce too much noise? max.hirschhorn |
| Comment by Judah Schvimer [ 01/Jul/19 ] |
|
vlad.rachev, are this log and this log not sufficient? |