Proper exit status handling of external cluster

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

Status

Assignee

Jakub Hava

Reporter

Avkash Chauhan

Labels

None

CustomerVisible

No

testcase 1

None

testcase 2

None

testcase 3

None

h2ostream link

None

Affected Spark version

None

AffectedContact

None

AffectedCustomers

AffectedPilots

None

AffectedOpenSource

None

Support Assessment

Platform Issue

Customer Request Type

Support Incident

Support ticket URL

None

End date

None

Baseline start date

None

Baseline end date

None

Task progress

None

Task mode

None

Fix versions

Priority

Major
Configure