Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-4635

Topology related jobs shouldn't be scheduled if topology is unclear/not available

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Commons Scheduler 2.4.6
    • Fix Version/s: Commons Scheduler 2.4.8
    • Component/s: Commons
    • Labels:
      None

      Description

      If a job is scheduled to be run only on the leader or only on a single instance, it is currently scheduled even if the topology is not available or changing.
      This is wrong as this can lead to the job being scheduled more than once in a cluster in such situations.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cziegeler Carsten Ziegeler
                Reporter:
                cziegeler Carsten Ziegeler
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: