Get rid of writeConfigServerDirect for writes to the ConfigServer database

XMLWordPrintableJSON

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

      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
            Reporter:
            Eric Maynard (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: