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

Get rid of writeConfigServerDirect for writes to the ConfigServer database

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Sharding 2020-11-30, Sharding 2020-12-14
    • 17

      https://github.com/mongodb/mongo/blob/master/src/mongo/s/catalog/sharding_catalog_client_impl.cpp#L771-L779

      Note that policy is labelled not idempotent, but it seems like there is a case when the write can be applied more than once in the server as seen on the linked BF. Investigate whether isNotPrimaryError it is actually safe to retry with this error.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            eric.maynard@mongodb.com Eric Maynard
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: