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

Make it possible to adjust the period of active jobs in the PeriodicRunner

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.10, 4.0.12
    • Component/s: None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0
    • Sprint:
      Service Arch 2019-03-25, Service Arch 2019-04-08

      Description

      There are startup+runtime settable server parameters that affect the period of jobs on the PeriodicRunner. Currently the periodic job to abort expired transactions uses a static variable hack inside the job to get around a non-adjustable job period. SERVER-31767 may be introducing another.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39936 Use PeriodicRunner handles to simplify shutdown ordering

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-31767 Provide a window of snapshot history that is accessible for PIT reads

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33295 Kill long-running snapshot transactions

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              jason.carey Jason Carey
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: