Uploaded image for project: 'SW'
  1. SW-365

Proper exit status handling of external cluster

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.10, 2.1.4, 2.0.8
    • Component/s: None
    • Labels:
      None
    • CustomerVisible:
      No
    • Sprint:
    • AffectedCustomers:
    • Support Assessment:
      Platform Issue
    • Customer Request Type:
      Support Incident

      Description

      On calling context.stop() on a SW H2O external cluster started in Yarn the application gets killed with state=KILLED and finalStatus=KILLED in yarn, this makes it impossible to discern between end states of H2O clusters without adding extra logic (which is unreliable).

      In this particular scenario the correct end state would be state=FINISHED finalStatus=SUCCEEDED

        Attachments

          Activity

            People

            • Assignee:
              Kuba Jakub Hava
              Reporter:
              avkash Avkash Chauhan (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: