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

Investigate behavioural change between 2.6 and 2.8 in stepDown

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.7.8
    • Component/s: Replication
    • ALL

      Not sure if it's a bug. I'm labeling as that for the time being.
      Run stepDown.py from here: https://github.com/dcci/mongo-replication-perf
      The test completes on 2.6, but not on 2.8.

      $ python stepDown.py --cfg spawn-examples/example-3nodes.json                                                                                                                                                                           
      localhost:30003 0.943552017212
      command SON([('replSetStepDown', 30)]) failed: No electable secondaries caught up as of 2014-10-29T20:39:39.348+0000
      {u'hosts': [u'localhost:30001', u'localhost:30002', u'localhost:30003'],
       u'ismaster': True,
       u'localTime': datetime.datetime(2014, 10, 29, 20, 39, 39, 348000),
       u'maxBsonObjectSize': 16777216,
       u'maxMessageSizeBytes': 48000000,
       u'maxWireVersion': 3,
       u'maxWriteBatchSize': 1000,
       u'me': u'localhost:30003',
       u'minWireVersion': 0,
       u'ok': 1.0,
       u'primary': u'localhost:30003',
       u'rbid': 1124988512,
       u'secondary': False,
       u'setName': u'rs0',
       u'setVersion': 1}
      

      mongod logs attached.

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            davide.italiano Davide Italiano
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: