The scripts and the masters/slaves files are only relevant to the scripts
which SSH to the machines to start/stop the processes. They have not really
an impact on how the processes find each other.
Calling them repeatedly and editing them can start additional processes, or
not stop all processes.
Hi Marc,
the master, i.e. JobManager, does not need to know which clients, i.e.
TaskManager, are supposed to connect to it. Indeed, only the task managers
need to know where to connect to and they will try to establish that
connection and re-connect when losing it.
Nico
On Friday, 11 August 2
Hi Greg,
I guess I restarted the cluster too fast. Combined with a high cpu inside the
cluster.
I tested it again few minutes ago and there was no issue! With „$ jps“ I
checked if there any Java process -> there wasn’t
But if the master don’t know slave5, how can slave5 reconnect to the
JobMan
Hi Marc,
By chance did you edit the slaves file before shutting down the cluster? If so,
then the removed worker would not be stopped and would reconnect to the
restarted JobManager.
Greg
> On Aug 11, 2017, at 11:25 AM, Kaepke, Marc wrote:
>
> Hi,
>
> I have a cluster of 4 dedicated machin
I start my cluster with:
bigdata@master:/usr/lib/flink-1.3.2$ ./bin/start-cluster.sh
Starting cluster.
Starting jobmanager daemon on host master.
Starting taskmanager daemon on host master.
Starting taskmanager daemon on host slave1.
Starting taskmanager daemon on host slave3.
And if I stop it:
b
