Ewen
> Date:03/16/2015 1:09 AM (GMT-08:00)
> To: user@flink.apache.org
> Subject: Re: Scaling a Flink cluster
>
> Hi Emmanuel!
>
> The slaves file is not needed on every node. It is only used by the
> "start-cluster.sh" Script, which makes an ssh call to every host i
@flink.apache.org
Subject: Re: Scaling a Flink cluster
Hi Emmanuel!
The slaves file is not needed on every node. It is only used by the
"start-cluster.sh" Script, which makes an ssh call to every host in that
file to start a taskmanager.
You can add a taskmanager to an existing flink cluster by simp
Hi Emmanuel!
The slaves file is not needed on every node. It is only used by the
"start-cluster.sh" Script, which makes an ssh call to every host in that
file to start a taskmanager.
You can add a taskmanager to an existing flink cluster by simply calling
"taskmanager.sh start" on that machine (w
On 16 Mar 2015, at 08:27, Emmanuel wrote:
> Hello,
>
> In my understanding, the flink-conf.yaml is the one config file to configure
> a cluster.
> The slave file lists the slave nodes.
> they must both be on every node.
The slaves file is only used for the startup script when using the
bin/s
Hello,
In my understanding, the flink-conf.yaml is the one config file to configure a
cluster.The slave file lists the slave nodes.they must both be on every node.
I'm trying to understand what is the best strategy to scale a Flink cluster
since:- adding a node means adding an entry to the slave
