Details

    • Type: New Feature
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: 1.4.1
    • Labels:
      None
    • Patch included:
      Yes
    • Magnolia Release:
      4.4.2

      Description

      When a job takes a long time to execute but is scheduled often, it might be desirable to avoid concurrent executions of the job.

      It seems like implementing the StatefulJob interface could be enough to achieve this. Here's a simple patch that allows Magnolia jobs to be configured as non-concurrent.

      To review: implications of this change:

      1. should we make this the default behavior ? (attached patch keeps the concurrent flag to true, i.e. the current default behavior)
      2. do we use a store for our jobs, should we, especially if we're starting to have long-running jobs ?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pbaerfuss Philipp Bärfuss
                Reporter:
                gjoseph Magnolia International
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: