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

do not update the replication progress map when receiving a heartbeat from primary

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.8.0-rc3
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL

      TEST HISTORY

      EARLIEST KNOWN FAILURE

       m31002| 2014-12-07T13:06:08.412-0500 [initandlisten] connection accepted from 10.168.209.60:47814 #21 (7 connections now open)
       m31002| 2014-12-07T13:06:08.412-0500 [initandlisten] connection accepted from 10.168.209.60:47813 #22 (8 connections now open)
       m31002| 2014-12-07T13:06:08.413-0500 [conn1] command write_concern_few_arbiters.$cmd command: insert { insert: "foo", documents: [ { _id: ObjectId('5484970fa3cd07836941245c'), x: 13.0 } ], ordered: true, writeConcern: { w: "majority", wtimeout: 9000.0 } } keyUpdates:0 numYields:0 locks(micros) w:4 reslen:80 1003ms
      assert: no write error: { "nInserted" : 1 }
      Error: no write error: { "nInserted" : 1 }
          at Error (<anonymous>)
          at doassert (src/mongo/shell/assert.js:11:14)
          at Function.assert.writeError (src/mongo/shell/assert.js:421:9)
          at /data/mci/shell/src/jstests/multiVersion/w_majority_change.js:144:12
          at /data/mci/shell/src/jstests/multiVersion/w_majority_change.js:153:2
      

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            ian@mongodb.com Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: