Thanks for the support! I created a Jira issue and PR:
- https://issues.apache.org/jira/browse/FLINK-18377
- https://github.com/apache/flink/pull/12723
Best,
Aljoscha
On 18.06.20 16:28, Marta Paes Moreira wrote:
+1
I've found the term Flink Master a tad bit confusing myself, in the past,
+1
I've found the term Flink Master a tad bit confusing myself, in the past,
as it's not used consistently throughout the documentation (as you mention).
Thanks for following up on this, Aljoscha!
On Wed, Jun 17, 2020 at 5:16 PM Robert Metzger wrote:
> Thanks a lot for looking into this!
>
>
Thanks a lot for looking into this!
+1 to your proposal
On Wed, Jun 17, 2020 at 10:55 AM David Anderson
wrote:
> Aljoscha,
>
> I think this is a step in the right direction.
>
> In some cases it may be difficult to talk concretely about the
> differences between different deployment models
Aljoscha,
I think this is a step in the right direction.
In some cases it may be difficult to talk concretely about the
differences between different deployment models (e.g., comparing a k8s
per-job cluster to a YARN-based session cluster, which is something I
typically present during training)
Hi Aljoscha,
sounds good to me. Let’s also make sure we don’t refer to the JobMaster as
Jobmanager anywhere then (code, config).
I am not sure we can avoid mentioning the Flink ResourceManagers in user
facing docs completely. For JobMaster and Dispatcher this seems doable.
Best,
Konstantin
On
Hi All,
This came to my mind because of the master/slave discussion in [1] and
the larger discussions about inequality/civil rights happening right now
in the world. I think for this reason alone we should use a name that
does not include "master".
We could rename it back to JobManager,
