[
https://issues.apache.org/jira/browse/SAMZA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jake Maes updated SAMZA-865:
----------------------------
Attachment: DESIGN-SAMZA-865-3.md
DESIGN-SAMZA-865-3.pdf
Great feedback, thanks!
[~nickpan47]
1. You're right, the design doc wasn't clear on this. In fact, the REST service
is mostly geared toward the "Samza-as-a-service" model, which is more likely to
focus on a hosted service rather than standalone. I clarified that the real use
case is to have a common API regardless of the underlying cluster
implementation, so as to enable generic tools, dashboards, etc.
2. Great suggestions. Added them.
3. That's right. I suppose I mentioned it in case any "rebels" decided to use
an older version. But if that happens, they may also encounter other problems
due to the YARN version. It has been removed.
4. I was worried these would make it too verbose, but it's not too bad. See
version 2 of the design doc.
5. Yes. Actually the doc was conflating the "central hosts" and RM hosts. In
the event that they're separate hosts, the Installation Finder can be adapted
to discover jobs wherever they are stored.
6. Good point. The "Packaging" wiki only calls out that the configuration is
NOT part of the job package. I'll update the design doc to describe the default
assumption and that the InstallationFinder can be used to adapt to any
deviation.
[~xinyu], thanks, I totally missed that!
> REST API for starting and stopping Samza jobs.
> -----------------------------------------------
>
> Key: SAMZA-865
> URL: https://issues.apache.org/jira/browse/SAMZA-865
> Project: Samza
> Issue Type: New Feature
> Reporter: Jake Maes
> Assignee: Jake Maes
> Labels: design
> Attachments: DESIGN-SAMZA-865-1.md, DESIGN-SAMZA-865-1.pdf,
> DESIGN-SAMZA-865-2.md, DESIGN-SAMZA-865-2.pdf, DESIGN-SAMZA-865-3.md,
> DESIGN-SAMZA-865-3.pdf
>
>
> The shell scripts we currently use to start and stop jobs are mostly specific
> to YARN and are not well documented APIs. This puts some burden on
> developers, which may develop a Samza solution with a YARN alternative or try
> to integrate Samza with other services like dashboards.
> This ticket is to discuss the addition of a REST API to start, stop and get
> status for jobs. Such an API could be extended for other use cases like
> modifying checkpoints, getting stack traces, getting logs, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
