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

shard_existing_coll_chunk_count.js should restart both mongod and mongos after changing max chunk size

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • 0

      In the last stable suite, with a last-stable mongos it's necessary to add back this line.

            Assignee:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Reporter:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: