[
https://issues.apache.org/jira/browse/FLINK-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-7040:
---------------------------------
Description:
With the new Flip-6 architecture, the client will communicate with the cluster
in a RESTful manner.
The cluster shall support the following REST calls:
* List jobs (GET): Get list of all running jobs on the cluster
* Submit job (POST): Submit a job to the cluster (only supported in session
mode)
* Lookup job leader (GET): Gets the JM leader for the given job
* Get job status (GET): Get the status of an executed job (and maybe the
JobExecutionResult)
* Cancel job (PUT): Cancel the given job
* Stop job (PUT): Stops the given job
* Take savepoint (POST): Take savepoint for given job (How to return the
savepoint under which the savepoint was stored? Maybe always having to specify
a path)
* Get KV state (GET): Gets the KV state for the given job and key (Queryable
state)
The first four REST calls will be served by the REST endpoint running in the
application master/cluster entrypoint. The other calls will be served by a REST
endpoint running along side to the JobManager.
Detailed information about different implementations and their pros and cons
can be found in this document:
https://docs.google.com/document/d/1eIX6FS9stwraRdSUgRSuLXC1sL7NAmxtuqIXe_jSi-k/edit?usp=sharing
was:In order to implement a dispatcher component/session runner, we have to
define its interface with which the client interacts. The interface definition
should contain the set of supported operations (e.g. submitJob, list jobs,
etc.) and which component communicates with which other component (e.g. will
the client directly talk to JobManagers when invoking job specific operations
(cancel job) or will it be forwarded by the dispatcher?).
> Flip-6 client-cluster communication
> -----------------------------------
>
> Key: FLINK-7040
> URL: https://issues.apache.org/jira/browse/FLINK-7040
> Project: Flink
> Issue Type: New Feature
> Components: Cluster Management, Mesos
> Reporter: Till Rohrmann
> Priority: Critical
> Labels: flip-6
>
> With the new Flip-6 architecture, the client will communicate with the
> cluster in a RESTful manner.
> The cluster shall support the following REST calls:
> * List jobs (GET): Get list of all running jobs on the cluster
> * Submit job (POST): Submit a job to the cluster (only supported in session
> mode)
> * Lookup job leader (GET): Gets the JM leader for the given job
> * Get job status (GET): Get the status of an executed job (and maybe the
> JobExecutionResult)
> * Cancel job (PUT): Cancel the given job
> * Stop job (PUT): Stops the given job
> * Take savepoint (POST): Take savepoint for given job (How to return the
> savepoint under which the savepoint was stored? Maybe always having to
> specify a path)
> * Get KV state (GET): Gets the KV state for the given job and key (Queryable
> state)
> The first four REST calls will be served by the REST endpoint running in the
> application master/cluster entrypoint. The other calls will be served by a
> REST endpoint running along side to the JobManager.
> Detailed information about different implementations and their pros and cons
> can be found in this document:
> https://docs.google.com/document/d/1eIX6FS9stwraRdSUgRSuLXC1sL7NAmxtuqIXe_jSi-k/edit?usp=sharing
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
