Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CABSbGk0wH=iD=1gfQ79TdyqMAafgo=T1x9C70TD5JnLjsynA7g@mail.gmail.com>
References: 
 <CABSbGk0wH=iD=1gfQ79TdyqMAafgo=T1x9C70TD5JnLjsynA7g@mail.gmail.com>
From: Maximilian Michels <mxm@apache.org>
Date: Wed, 17 Feb 2016 10:11:38 +0100
Message-ID: 
 <CAGco--aAbRNVdgWBrLFo7c0pJyEdBc5hds5AwsRdb5qKPuAFGA@mail.gmail.com>
Subject: Re: Adding TaskManager's
To: dev@flink.apache.org
Content-Type: text/plain; charset=UTF-8

Hi Deepak,

The job manager doesn't have to know about task managers. They will
simply register at the job manager using the provided configuration.
In HA mode, they will lookup the currently leading job manager first
and then connect to it. The job manager can then assign work.

Cheers,
Max

On Tue, Feb 16, 2016 at 10:41 PM, Deepak Jha <dkjhanitt@gmail.com> wrote:
> Hi All,
> I have a question on scaling-up/scaling-down flink cluster.
> As per the documentation, in order to scale-up the cluster, I can add a new
> taskmanager on the fly and jobmanager can assign work to it. Assuming, I
> have Flink HA , so in the event of master JobManager failure, how is this
> taskmanager detail is going to get transferred ? I believe new master will
> just read the contents from slaves config file. Can anyone give more
> clarity on how this is done ? Or, Is it union of slaves and the
> taskmanager's that are added on the fly ?
>
> --
> Thanks,
> Deepak