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

mongod fasserts in auto_rebalance.js on sharding_legacy

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 12 (04/01/16)

      I'm working on catching mongod processes that exit with a non-zero exit code (see SERVER-20838), and auto_rebalance.js fails on sharding_legacy_op_query_WT:

      https://logkeeper.mongodb.org/build/568c46adbe07c46e4d3d514b/test/568c4990be07c46e4d3da3d7#L1666

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            jonathan.reams@mongodb.com Jonathan Reams
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: