Make PeriodicJob stop before TimestampMonitor destroy its members

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.8
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-06-15
    • 25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The issue is fixed for versions after v4.2 by SERVER-42374. We should apply the same reordering to v4.2 to prevent the periodic runner from addressing TimestampMonitor members after their destruction.

              Assignee:
              Gregory Wlodarek
              Reporter:
              Amirsaman Memaripour
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: