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

No sharding metadata changes should be allowed if config servers are inconsistent

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.6, 2.6.8
    • Sharding
    • None
    • ALL

    Description

      Currently if a config server inconsistency is detected, we only disallow starting new mongoS'es, autosplits and the balancer. However, sharding new collections/databases is allowed, as well as manual chunk splits and moves.

      Ongoing manual metadata operations are often triggered by scripts, so if they are not failing it's not possible to detect the erroneous condition.

      Further, it's not possible to predict the full scope consequences of metadata alterations when config servers are not consistent.

      Attachments

        Activity

          People

            Unassigned Unassigned
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: