-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Due to the logic in VoteRequester::Algorithm::processResponse(), log messages can be strung together erroneously, as in the following example:
[js_test:query_config] 2016-10-13T17:07:32.254+0000 c20762| 2016-10-13T17:07:32.253+0000 I REPL [ReplicationExecutor] VoteRequester(term 0 dry run) received an invalid response from ip-10-169-236-36:20763: BadValue: Unexpected field info in ReplSetRequestVotesreceived a no vote from ip-10-169-236-36:20763 with reason ""; response message: { info: "run rs.initiate(...) if not yet done for the set", ok: 0.0, errmsg: "no replset config has been received", code: 94, codeName: "NotYetInitialized" }
This log message ought to end at "ReplSetRequestVotes", but instead falls through into the "received a no vote..." erroneously. The trailing "response message:" is, however, correct.
- duplicates
-
SERVER-46107 Manual conversion of logs
-
- Closed
-