You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/31 18:46:41 UTC
[jira] [Commented] (SAMZA-1089) JobRunner should support kill and
status commands.
[ https://issues.apache.org/jira/browse/SAMZA-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951480#comment-15951480 ]
ASF GitHub Bot commented on SAMZA-1089:
---------------------------------------
GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/106
SAMZA-1089: Runner should support kill and status commands
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jmakes/samza samza-1089-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/106.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #106
----
commit 86fe6fdd65bc670692fde57b35c50b05604f9436
Author: Jacob Maes <jm...@linkedin.com>
Date: 2017-03-30T19:22:10Z
SAMZA-1089: Runner should support kill and status commands
----
> JobRunner should support kill and status commands.
> --------------------------------------------------
>
> Key: SAMZA-1089
> URL: https://issues.apache.org/jira/browse/SAMZA-1089
> Project: Samza
> Issue Type: Task
> Reporter: Jake Maes
> Assignee: Jake Maes
>
> The JobRunner is the central place to launch Samza jobs. We use run-job.sh to invoke the JobRunner, which then launches the job as described here:
> http://samza.apache.org/learn/documentation/0.11/jobs/job-runner.html
> Note that the JobRunner works for any job that implements the StreamJob interface, so it works with YarnJob, ProcessJob, and so on.
> However, to kill or get the status for a job, we only have a set of YARN-specific scripts.
> Since the StreamJobs all implement the kill() and getStatus() methods, there's no reason we can't similarly leverage the StreamJob abstraction to perform these operations as well.
> The proposal is to update JobRunner to support all 3 commands.
> The benefits are:
> 1. A common abstract way to start, stop, and get status for any type of StreamJob.
> 2. For features like multistage (samza-1041), this will be a much easier way to collectively manage a set of processors as separate (e.g. YARN) applications
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)