Do not reset KeysCollectionManager

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.6, 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • v3.6
    • Sharding 2018-05-21
    • 4
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      KeysCollectionManager may be referenced after it was reset when a node is transitioning to arbiter but processing older requests.

      There is no need to reset it because  the arbiter nodes can not transition to a non arbiters.

              Assignee:
              Misha Tyulenev (Inactive)
              Reporter:
              Misha Tyulenev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: