[FLINK-4897] Implement Dispatcher to support Flink sessions

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: Deployment / Mesos, Runtime / Coordination
• Labels: flip-6

Environment

FLIP-6 feature branch

• Assignee: Till Rohrmann
• Reporter: Eron Wright
• Created: 24/Oct/16 23:00
• Updated: 28/Feb/19 14:13
• Resolved: 13/Jul/18 06:36

Description

This task is to implement the dispatcher component which reacts to calls from the cluster's REST endpoint.

The dispatcher is responsible for job submission, job listing, job leader lookups, restarting jobs in case of a recovery and the cluster's component lifecycle management.

Issue Links

• blocks: FLINK-4319 Rework Cluster Management (FLIP-6)
• depends upon: FLINK-7072 Create RESTful cluster endpoint
• is depended upon by: FLINK-7082 Flip-6: Generic entry point for Flink sessions
• is depended upon by: FLINK-7075 Implement Flip-6 standalone mode

Sub-Tasks

• Refactor HTTP handlers and Netty server/client: Closed
• Implement skeletal structure of dispatcher component: Closed
• Pass in proper Configuration to Dispatcher component: Closed
• Fence Dispatcher: Closed
• Create Dispatcher REST endpoint: Closed
• Cache JobExecutionResult from finished JobManagerRunners: Closed
• Make JobExecutionResult accessible in per-job cluster mode: Closed