Implement Reliable, Isolated & Unified Job Submission
summary
A platform running over Flink manages ~1,200 jobs that process ~35 trillion messages and ~4.5 PB/day and replaces flaky ad hoc submission with an atomic protocol: job graph persistence in the job-graph store marks successful submission, only the dispatcher writes the job-registry to avoid races, and finished states are archived rather than eagerly cleared to prevent duplicates; this uses transactional high-availability services, adds an application mode for server-side compilation and dependency localization, and exposes layered clients (deployer, cloud client, job client).
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:30Outline
- 0:57Oceanus: Tencent Real-Time Compute Platform
- 2:13Cluster Deployment(Session Mode)
- 3:20Job Submission(Session Mode)
- 6:30Cluster Deployment(Job Mode)
- 8:34Failure Case: Job Manager failed to start in time
- 9:38Failure Case: Job Manager crashed after job finished
- 11:25What to define job submitted & executed
- 12:56How to achieve atomic job submission
- 16:09Drawbacks
- 18:24Application Mode: Package User Program
- 19:20Application Mode: Prepare Dependencies
- 20:10Application Mode: Cluster Deployment
- 20:25Application Mode: Download Dependencies
- 20:53Application Mode: Execute in Isolation
- 21:38Deployment: Recap
- 23:07Client Interface: The Problem
- 24:01Client Interface: Three-Layers Architecture
- 25:08Client Interface: Deployer
- 25:56Client Interface: Cluster Client
- 27:03Client Interface: Job Client
- 28:04User Case: Platform
- 29:12User Case: End-User
related talks
38mBuilding Unified Streaming Platform at Uber
40mGrowing a managed Flink streaming platform from scratch
37mBuilding and operating large-scale streaming applications at King
35mApache Flink 2.0: Unified Enterprise Data Processing System and Beyond
43mStream Processing and Applications in the Modern Age
44mFlink’s New Batch Architecture
37mKeynote | Flink Ahead: What Comes After Unified Batch & Streaming?
24mStateful Functions: Flexible like a Microservice, Consistent like a Monolith
