Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAHNHubY91MhpUfM=hZA4nNhPDoLFqYin4G_Kcoetq=eTkS_M7w@mail.gmail.com>
References: 
 <CAHNHubZNvp9U4J56hF=Wn8UYAPzPSfeM7Nu-60DFuXZ2rT2U3Q@mail.gmail.com>
	<CAHNHubY91MhpUfM=hZA4nNhPDoLFqYin4G_Kcoetq=eTkS_M7w@mail.gmail.com>
Date: Thu, 20 Aug 2015 11:34:41 +0530
Message-ID: 
 <CACc2-Yu_EGbYfVa3vSusYDYtitaYgW2k5baitgv-55_v1AN3hg@mail.gmail.com>
Subject: Re: App Master takes ~30min to re-schedule task attempts.
From: Susheel Kumar Gadalay <skgadalay@gmail.com>
To: user@hadoop.apache.org
Content-Type: text/plain; charset=UTF-8

Change mapreduce.reduce.shuffle.connect.timeout,
mapreduce.reduce.shuffle.read.timeout.
By default they are 180000.

On 8/20/15, manoj <manojm.321@gmail.com> wrote:
> Hello all,
>
> I'm running Apache2.6.0.
> I'm trying to remove a node from a Hadoop Cluster and the add it back.
> The taskattempts on the node which was removed are rescheduled only after
> 30min.
>
> During this 30min period looks like the App Master is trying to connect(
> check the log below ) the same node which was removed and after about 30min
> it reschedules those taskAttempts from the lost node and eventually the job
> succeeds.
>
> how can I reduce the 30min wait time?
>
> .....
> ......
> 2015-08-14 11:25:21,662 INFO [ContainerLauncher #7]
> org.apache.hadoop.ipc.Client: Retrying connect to server:
> host172/XX.XX.XX.XX:36158. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> ......
> ......
>
> Thanks
> --Manoj Kumar M
>