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

Segmentation fault in mongos when config servers not available

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.8
    • Fix Version/s: 3.2.9
    • Component/s: Sharding
    • Labels:
    • Environment:
      Ubuntu 14.04 x64 on Hyper-V 2012R2 w/Docker 1.12
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      Create an CSRS and start mongos:
      /usr/bin/mongos --configdb config/config-0:27017,config-1:27017,config-2:27017

      Show
      Create an CSRS and start mongos: /usr/bin/mongos --configdb config/config-0:27017,config-1:27017,config-2:27017
    • Sprint:
      Sharding 18 (08/05/16)

      Description

      Mongos crashes on startup occasionally (3 out of 10 times so far).
      Logs are attached.

        Attachments

        1. mongos-0.log
          22 kB
        2. mongos-1.log
          21 kB

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25161 MongoDB sharding data node crashed when adding new config server

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25317 [mongosMain] Invalid access at address: 0x10e4000

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-7553 mongos crashes when configdb is not listening to the port but waits when it cannot resolve the DNS

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: