Aljoscha
Sorry about late reply.
David and I drafted a design doc with some diagrams. We may not work on it
immediately, but we thought it would be valuable to share our thoughts and
hear feedbacks.
https://docs.google.com/document/d/1diHQyOPZVxgmnmYfiTa6glLf-FlFjSHcL8J3YR2xLdk/edit#heading=h.12
Elias Levy created FLINK-4326:
-
Summary: Flink start-up scripts should optionally start services
on the foreground
Key: FLINK-4326
URL: https://issues.apache.org/jira/browse/FLINK-4326
Project: Flink
Suresh Krishnappa created FLINK-4325:
Summary: Implement Web UI HTTPS
Key: FLINK-4325
URL: https://issues.apache.org/jira/browse/FLINK-4325
Project: Flink
Issue Type: Sub-task
Suresh Krishnappa created FLINK-4324:
Summary: Enable Akka SSL
Key: FLINK-4324
URL: https://issues.apache.org/jira/browse/FLINK-4324
Project: Flink
Issue Type: Sub-task
Report
Stephan Ewen created FLINK-4323:
---
Summary: Checkpoint Coordinator Removes HA Checkpoints in Shutdown
Key: FLINK-4323
URL: https://issues.apache.org/jira/browse/FLINK-4323
Project: Flink
Issue T
Stephan Ewen created FLINK-4322:
---
Summary: Unify CheckpointCoordinator and SavepointCoordinator
Key: FLINK-4322
URL: https://issues.apache.org/jira/browse/FLINK-4322
Project: Flink
Issue Type:
Stephan Ewen created FLINK-4321:
---
Summary: Initialize TaskExecutions directly with their starting
state
Key: FLINK-4321
URL: https://issues.apache.org/jira/browse/FLINK-4321
Project: Flink
Iss
Let me rephrase my comment on the dispatcher.I mean that its API would be
job-centric, i.e. with operations like `execute(jobspec)` rather than
operations like `createSession` that the status-quo would suggest.
Since writing those comments I’ve put more time into developing the Mesos
dispa
Stephan Ewen created FLINK-4320:
---
Summary: Fix misleading ScheduleMode names
Key: FLINK-4320
URL: https://issues.apache.org/jira/browse/FLINK-4320
Project: Flink
Issue Type: Sub-task
Stephan Ewen created FLINK-4319:
---
Summary: Rework Cluster Management (FLIP-6)
Key: FLINK-4319
URL: https://issues.apache.org/jira/browse/FLINK-4319
Project: Flink
Issue Type: Improvement
@Aljoscha
I would not make the ResourceManager a subcomponent of the JobManager.
While that may be simpler initially, I would like to keep the door open to
let RM and JM run in different processes/nodes.
Also, for Yarn/Mesos sessions, the ResourceManager may run longer than the
JobManager.
On Su
Hi Eron!
Some comments on your comments:
*Dispatcher*
- The dispatcher should NOT be job-centric. The dispatcher should take
over the "multi job" responsibilities here, now that the JobManager is
single-job only.
- An abstract dispatcher would be great. It could implement the
connection/HTTP
Ufuk Celebi created FLINK-4318:
--
Summary: Make master docs build target version-specific
Key: FLINK-4318
URL: https://issues.apache.org/jira/browse/FLINK-4318
Project: Flink
Issue Type: Improvem
Ufuk Celebi created FLINK-4317:
--
Summary: Restructure documentation
Key: FLINK-4317
URL: https://issues.apache.org/jira/browse/FLINK-4317
Project: Flink
Issue Type: Improvement
Compone
Stephan Ewen created FLINK-4316:
---
Summary: Make flink-core independent of Hadoop
Key: FLINK-4316
URL: https://issues.apache.org/jira/browse/FLINK-4316
Project: Flink
Issue Type: Bug
C
Stephan Ewen created FLINK-4315:
---
Summary: Remove Hadoop Dependency from flink-java
Key: FLINK-4315
URL: https://issues.apache.org/jira/browse/FLINK-4315
Project: Flink
Issue Type: Sub-task
Ufuk Celebi created FLINK-4314:
--
Summary: Test instability in
JobManagerHAJobGraphRecoveryITCase.testJobPersistencyWhenJobManagerShutdown
Key: FLINK-4314
URL: https://issues.apache.org/jira/browse/FLINK-4314
17 matches
Mail list logo
