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

Increase verbosity on sharding/remove2.js and make timeout so high that we get a stack dump -- temporarily to help diagnose test failure.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-05-08

    Description

      Increase the verbosity to try and get more information on what's happening in the sharding system – BF-5335 isn't logging much of anything, so we can't see what's happening, if anything.

      Also increase the assert.soon to greater than 2 hours so we get stack dumps and can make sure we didn't add any deadlocks somewhere recently.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: