Re: Problem starting taskexecutor daemons in 3 node cluster

2019-09-17 Thread Till Rohrmann
SSH access to the nodes and nodes being able to talk to each other are separate issues. The former is only used for starting the Flink cluster. Once the cluster is started, Flink only requires that nodes can talk to each other (independent of SSH). Cheers, Till On Tue, Sep 17, 2019 at 7:39 AM

Re: Problem starting taskexecutor daemons in 3 node cluster

2019-09-16 Thread Komal Mariam
Hi Till, Thank you for the reply. I tried to ssh each of the nodes individually with each other and they all can connect to each other. Its just that all the other worker nodes cannot for some reason. connect to the job manager on 150.82.218.218:6123. (Node 1) I got around the problem by

Re: Problem starting taskexecutor daemons in 3 node cluster

2019-09-13 Thread Till Rohrmann
Hi Komal, could you check that every node can reach the other nodes? It looks a little bit as if the TaskManager cannot talk to the JobManager running on 150.82.218.218:6123. Cheers, Till On Thu, Sep 12, 2019 at 9:30 AM Komal Mariam wrote: > I managed to fix it however ran into another

Re: Problem starting taskexecutor daemons in 3 node cluster

2019-09-12 Thread Komal Mariam
I managed to fix it however ran into another problem that I could appreciate help in resolving. it turns out that the username for all three nodes was different. having the same username for them fixed the issue. i.e same_username@slave-node2-hostname same_username@slave-node3-hostname

Problem starting taskexecutor daemons in 3 node cluster

2019-09-10 Thread Komal Mariam
I'm trying to set up a 3 node Flink cluster (version 1.9) on the following machines: Node 1 (Master) : 4 GB (3.8 GB) Core2 Duo 2.80GHz, Ubuntu 16.04 LTS Node 2 (Slave) : 16 GB, Core i7-3.40GHz, Ubuntu 16.04 LTS Node 3 (Slave) : 16 GB, Core i7-3,40GHz, Ubuntu 16.04 LTS I have followed the