Why does Flink do resource management by only slots, not by TaskManagers
and slots?
If there are one Flink cluster to submit multiple jobs, how do I make
JobManager to distribute subtasks evenly to all TaskManagers?
Now, JobManager treats the slots globally, some jobs' operators are
assigned only
e.g. running
> JobManager or TaskManager instances? Also that you're not accidentally
> running
> the yarn-session.sh script of 1.3?
>
>
> Nico
>
> On Wednesday, 6 September 2017 06:36:42 CEST Sunny Yun wrote:
>> Hi,
>>
>> Using flink 1.2.0, I faced t
ething might be mixed up between
> (remaining artefacts of) flink 1.3 and 1.2.Can you verify that nothing of
> your flink 1.3 tests remains, e.g. running JobManager or TaskManager
> instances? Also that you're not accidentally running the yarn-session.sh
> script of 1.3?NicoOn Wednesday,
Hi,
Using flink 1.2.0, I faced to issue
https://issues.apache.org/jira/browse/FLINK-6117
https://issues.apache.org/jira/browse/FLINK-6117.
This issue is fixed at version 1.3.0. But I have some reason to trying to
find out work around.
I did,
1. change source according to
https://github.com/apache
I am still struggling to solve this problem.
I have no doubt that the JOB should automatically restart after restarting
the TASK MANAGER in YARN MODE. Is it a misunderstood?
Problem seems that *JOB MANAGER still try to connect to old TASK MANAGER
even after new TASK MANAGER container be created.*
