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

Do not reset KeysCollectionManager

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.6, 4.0.0-rc0
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2018-05-21
    • Linked BF Score:
      4

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            misha.tyulenev Misha Tyulenev
            Reporter:
            misha.tyulenev Misha Tyulenev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: