Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19706

More gracefully handle the job execution status during a server crash.

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Batch
    • ---
    • ---

      Currently, the batch subsystem behaves like these:

      • If a job is {}not stopped{} during a "server crash", then the job will always be kept in STARTED status.
      • If a job is {}stopped{} during a "server crash", then the job will be moved into UNKNOWN status.
      • If a {}crashed{} job stays in STARTED status and is stopped after a "server restart", the job will be moved into UNKNOWN status.
      • The UNKNOWN job can’t be restarted manually in the Admin Console. (I haven't checked the CLI side)

      The current implementation could be improved in these places:

      • No matter whether a job is {}stopped{} or not during a "server crash", the job {}shouldn’t{} be kept in UNKNOWN status.
      • The STARTED job should be able to be stopped correctly, and it {}shouldn’t{} be moved to UNKNOWN status after manually stopping it.

       

        1. image_2_720.png
          image_2_720.png
          50 kB
        2. image_3_720.png
          image_3_720.png
          38 kB
        3. image_720.png
          image_720.png
          66 kB
        4. image.png
          image.png
          480 kB
        5. image 2.png
          image 2.png
          361 kB

              weli@redhat.com Weinan Li
              weli@redhat.com Weinan Li
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: