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

Make PeriodicJob stop before TimestampMonitor destroy its members

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

      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@mongodb.com Gregory Wlodarek
            Reporter:
            amirsaman.memaripour@mongodb.com Amirsaman Memaripour
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: