mongos needs to also refresh db version after receiving onImplicitCreate error

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Hide

      see db_ver.js

      Show
      see db_ver.js
    • Sharding 2018-08-13, Sharding 2018-09-10, Sharding 2018-09-24, Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19, Sharding 2019-02-25
    • 17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a mongos with stale db version tries to send a write to an unsharded collection to the wrong shard, it will trigger the onImplicit create error since the collection does not exist on the shard. It will perform a refresh on the collection version and retry again, but since the database version was not refreshed, it will be sent to the same wrong shard and hit the same error again. This will keep on happening until it ran out of retries.

            Assignee:
            Randolph Tan
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: