[SERVER-26342] Incorrect and misleading log message when blacklisting sync source because we are too stale Created: 26/Sep/16 Updated: 23/Nov/16 Resolved: 23/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Benety Goh |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
This log message says that remoteEarliestOptime is greater than earliestOpTimeSeen. That is incorrect as it is the opposite of the if-statement that causes the line to print. Switching the words "greater than" to "less than" make the log message correct, though it is still misleading in that case as it seems to imply that the fact that remoteEarliestOpTime is less than earliestOpTimeSeen had an effect on our decision to blacklist the sync source, which it did not, that is just an extra unrelated piece of information. |
| Comments |
| Comment by Benety Goh [ 02/Nov/16 ] |
|
Fixed in |