You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2017/05/01 18:24:04 UTC

[jira] [Created] (SAMZA-1250) JobRunner.kill doesn't terminate cleanly with YarnJob.

Jake Maes created SAMZA-1250:
--------------------------------

             Summary: JobRunner.kill doesn't terminate cleanly with YarnJob.
                 Key: SAMZA-1250
                 URL: https://issues.apache.org/jira/browse/SAMZA-1250
             Project: Samza
          Issue Type: Bug
            Reporter: Jake Maes
            Assignee: Jake Maes
             Fix For: 0.13.0


I discovered this while working on the wikipedia tutorial with the Fluent API. 

Running run-app.sh with --operation=kill will kill the job but doesn't appear to do so cleanly. There are a few reasons. 
1. The client can't get the status for finished jobs because it only looks at the active (RUNNING) application IDs
2. JobRunner.kill() waits for a successful finish. It should wait for any finish
3. A killed job is considered an unsuccessful finish. It should be considered successful.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)