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

No data found after force sync in no_chaining.js

    • Fully Compatible
    • ALL
    • Repl B (10/30/15), Repl C (11/20/15), Repl E (01/08/16)
    • 0

      Task
      Logs

      [js_test:no_chaining] 2015-10-13T14:45:11.165+0000 check that forcing sync target still works
      [js_test:no_chaining] 2015-10-13T14:45:11.166+0000 { "syncFromRequested" : "ip-10-97-195-239.ec2.internal:20268", "ok" : 1 }
      [js_test:no_chaining] 2015-10-13T14:45:11.892+0000 d20262| 2015-10-13T14:45:11.891+0000 I REPL     [ReplicationExecutor] syncing from: ip-10-97-195-239.ec2.internal:20268 by request
      ...
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 2015-10-13T14:45:19.856+0000 E QUERY    [thread1] Error: assert.soon failed, msg:Check for data after force sync :
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 doassert@src/mongo/shell/assert.js:15:14
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 assert.soon@src/mongo/shell/assert.js:194:13
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 forceSync/<@jstests/replsets/no_chaining.js:55:1
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 assert.soon@src/mongo/shell/assert.js:188:17
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 forceSync@jstests/replsets/no_chaining.js:50:1
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000 @jstests/replsets/no_chaining.js:77:5
      [js_test:no_chaining] 2015-10-13T14:45:19.858+0000
      [js_test:no_chaining] 2015-10-13T14:45:19.859+0000 failed to load: jstests/replsets/no_chaining.js
      

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: