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

sharding_rs1.js failed due to too stale condition

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • None
    • 3.1.9
    • None
    • None
    • Fully Compatible
    • ALL
    • RPL A (10/09/15)
    • 0

    Description

      This test failed due to a node falling behind and getting stale. The test should ensure this can't happen.

      test failure

      failures

      [js_test:sharding_rs1] 2015-10-03T14:53:47.524+0000 d20011| 2015-10-03T14:53:47.523+0000 I REPL     [ReplicationExecutor] syncing from: ip-10-232-149-173:20012
      [js_test:sharding_rs1] 2015-10-03T14:53:47.524+0000 d20012| 2015-10-03T14:53:47.524+0000 I NETWORK  [initandlisten] connection accepted from 10.232.149.173:54394 #11 (8 connections now open)
      [js_test:sharding_rs1] 2015-10-03T14:53:47.525+0000 d20012| 2015-10-03T14:53:47.524+0000 I NETWORK  [conn11] end connection 10.232.149.173:54394 (7 connections now open)
      [js_test:sharding_rs1] 2015-10-03T14:53:47.525+0000 d20011| 2015-10-03T14:53:47.524+0000 W REPL     [rsBackgroundSync] we are too stale to use ip-10-232-149-173:20012 as a sync source
      [js_test:sharding_rs1] 2015-10-03T14:53:47.525+0000 d20011| 2015-10-03T14:53:47.525+0000 I REPL     [ReplicationExecutor] syncing from: ip-10-232-149-173:20010
      

      Attachments

        Activity

          People

            matt.dannenberg Matt Dannenberg
            scotthernandez Scott Hernandez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: