[SERVER-13502] Log replica set configuration on changes Created: 07/Apr/14 Updated: 05/Feb/16 Resolved: 11/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | dnsf, elections | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Replication related events in logfiles can only be interpreted in the context of the replica set configuration at the time the line was logged. We log that reconfig events have occurred, both when we get a replSetReconfig command, and getting a new config from a remote, but not the actual configuration (either the previous or the new one). Logging the full contents of the before/after config documents whenever it changes would greatly assist with the correct interpretation of subsequent replSet events that occur in the logfile, particularly when there is limited/missing external information about the reconfigs that have occurred. |
| Comments |
| Comment by Eric Milkie [ 11/Jun/15 ] |
|
Replica set configurations are now logged in the system log when they change. |