[
https://issues.apache.org/jira/browse/SAMZA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125908#comment-15125908
]
Yi Pan (Data Infrastructure) commented on SAMZA-865:
----------------------------------------------------
Hi, [~jmakes], sorry for the late review. I took a look at the design doc and
it looks good overall. I have a few suggestions/questions listed below:
# For deployment tooling, what do you vision as the use case of “common
interface to start, stop, and list jobs … in a mixed environment”? It is a bit
hard to imagine how the RESTful APIs will work for standalone jobs where there
is no central team manage them.
# In Future Use Cases, the following could be good examples as well:
## Dynamic log level changes
## Dynamic configuration changes
# In the “Leverage YARN Resource Manager REST API” section: It requires a
minimum YARN version of 2.5.1 ==> we should remove this since we are already on
2.6.1 and above
# In the API design, it would be good to mention the error codes returned as
well, in addition to success responses
# A quick question: wouldn’t the abstraction of InstallationFinder also removes
the strict assumption that job packages are installed on a central host? It can
be imaged that there could be a “central” repository to register all installed
Samza job packages, not on a single host, then some script to download and
launch those jobs in Mesos or Kubernetes.
# It would also be good to mention how we expect the configuration be packaged
and deployed. This part is a little fuzzy in the design doc. The current
assumption is that the deployment of a job also include deployment of the
configuration from a “central repository” together w/ the job.
Thanks a lot!
> 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
> Labels: design
> Attachments: DESIGN-SAMZA-865-1.md, DESIGN-SAMZA-865-1.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)
