Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-1864

[EAP7] Support clean shutdown on TERM

    XMLWordPrintable

Details

    • 1
    • Hide
      Feature: Replaced the EAP7 image prestop hooks in application templates with a TERM signal handler in the EAP7 openshift-launch script.
      Reason: Relying on a prestop hook for clean shutdown of EAP7 on a TERM signal adds an extra 2 seconds to termination. A TERM handler in the openshift-launch scripts cleanly terminates the EAP7 images without the 2 second delay.
      Result : The openshift-launch script wrapper now sets a trap for a TERM signal, forks the EAP7 application process in the background, then waits for EAP process to terminate. When a TERM signal is given, the wrapper process catches the signal and runs the jboss-cli script to cleanly shutdown the EAP process.
           
      Show
      Feature: Replaced the EAP7 image prestop hooks in application templates with a TERM signal handler in the EAP7 openshift-launch script. Reason: Relying on a prestop hook for clean shutdown of EAP7 on a TERM signal adds an extra 2 seconds to termination. A TERM handler in the openshift-launch scripts cleanly terminates the EAP7 images without the 2 second delay. Result : The openshift-launch script wrapper now sets a trap for a TERM signal, forks the EAP7 application process in the background, then waits for EAP process to terminate. When a TERM signal is given, the wrapper process catches the signal and runs the jboss-cli script to cleanly shutdown the EAP process.      
    • CLOUD Maintenance Sprint 11

    Description

      At present we rely on a prestop hook to cleanly shutdown the EAP 7.x images, we should add in a wrapper script to handle clean shutdown on receipt of a TERM signal so the prestop hook is no longer necessary.

      Both mechanisms are impacted by the same termination period although there is an extra 2 second grace if the prestop hook is used.

      Attachments

        Issue Links

          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-1965 [SSO7] Support clean shutdown on TERM

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Feature Request - Feature requests from customers and/or users WFCORE-3073 Handle Shutdown via TERM gracefully

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2152 [tracker] Sprint 12 release

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kliberti Kyle Liberti
              kconner@redhat.com Kevin Conner (Inactive)
              Pavel Drobek Pavel Drobek
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: