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

Do not reset KeysCollectionManager

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.6, 4.0.0-rc0
    • Sharding
    • Fully Compatible
    • ALL
    • v3.6
    • Sharding 2018-05-21
    • 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

            misha.tyulenev@mongodb.com Misha Tyulenev
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: