Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20745

replSetElect response does not always contain 'vote' field

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Trivial - P5 Trivial - P5
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      It looks like it's possible for the replSetElect command response to not contain a 'vote' field:

      I REPL     [ReplicationExecutor] received EOO votes from ip-10-140-165-110:20018
      E REPL     [ReplicationExecutor] wrong type for vote argument in replSetElect command: EOO
      

      More context:

      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.130+0000 c20017| 2015-10-01T15:53:17.127+0000 I REPL     [ReplicationExecutor] This node is ip-10-140-165-110:20017 in the config
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.130+0000 c20017| 2015-10-01T15:53:17.127+0000 I REPL     [ReplicationExecutor] transition to STARTUP2
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.130+0000 c20018| 2015-10-01T15:53:17.128+0000 I NETWORK  [initandlisten] connection accepted from 10.140.165.110:33629 #6 (4 connections now open)
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.130+0000 c20018| 2015-10-01T15:53:17.128+0000 I COMMAND  [conn3] received elect msg { replSetElect: 1, set: "test-configRS", who: "ip-10-140-165-110:20016", whoid: 0, cfgver: 1, round: ObjectId('560d56ed99649624616c262a') }
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.131+0000 c20017| 2015-10-01T15:53:17.127+0000 I REPL     [ReplicationExecutor] Member ip-10-140-165-110:20016 is now in state SECONDARY
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.131+0000 c20017| 2015-10-01T15:53:17.128+0000 I COMMAND  [conn3] received elect msg { replSetElect: 1, set: "test-configRS", who: "ip-10-140-165-110:20016", whoid: 0, cfgver: 1, round: ObjectId('560d56ed99649624616c262a') }
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.131+0000 c20017| 2015-10-01T15:53:17.128+0000 I REPL     [ReplicationExecutor] replSetElect voting yea for ip-10-140-165-110:20016 (0)
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.132+0000 c20017| 2015-10-01T15:53:17.128+0000 I NETWORK  [conn3] end connection 10.140.165.110:57139 (1 connection now open)
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.132+0000 c20017| 2015-10-01T15:53:17.129+0000 I REPL     [ReplicationExecutor] Member ip-10-140-165-110:20018 is now in state STARTUP
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.132+0000 c20017| 2015-10-01T15:53:17.130+0000 I NETWORK  [initandlisten] connection accepted from 10.140.165.110:57156 #5 (2 connections now open)
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.132+0000 c20016| 2015-10-01T15:53:17.127+0000 I REPL     [ReplicationExecutor] Standing for election
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.133+0000 c20016| 2015-10-01T15:53:17.128+0000 I REPL     [ReplicationExecutor] running for election
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.133+0000 c20016| 2015-10-01T15:53:17.128+0000 I REPL     [ReplicationExecutor] received EOO votes from ip-10-140-165-110:20018
      [js_test:fsm_all_sharded_replication] 2015-10-01T15:53:17.133+0000 c20016| 2015-10-01T15:53:17.128+0000 E REPL     [ReplicationExecutor] wrong type for vote argument in replSetElect command: EOO
      

      This was spotted in the fsm_all_sharded_replication.js log from https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_debug_concurrency_sharded_WT_97128797aa2d5169ca2e7f1cc6795955857803d7_15_09_30_21_57_26.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            kamran.khan Kamran K. (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: