(ipc.client.connect.max.retries, 2);
and it still seems to wait about 15 seconds.
From: Jian He [mailto:j...@hortonworks.com]
Sent: Wednesday, February 12, 2014 3:44 PM
To: user@hadoop.apache.org
Subject: Re: very long timeout on failed RM connect
ipc.client.connect.retry.interval sets the underlying ipc retry
that can be set?
Thanks
John
From: John Lilley [mailto:john.lil...@redpoint.net]
Sent: Monday, February 10, 2014 12:12 PM
To: user@hadoop.apache.org
Subject: RE: very long timeout on failed RM connect
I tried:
conf.set(yarn.resourcemanager.connect.max-wait.ms, 1);
conf.set
:* Monday, February 10, 2014 12:12 PM
*To:* user@hadoop.apache.org
*Subject:* RE: very long timeout on failed RM connect
I tried:
conf.set(yarn.resourcemanager.connect.max-wait.ms, 1);
conf.set(yarn.resourcemanager.connect.retry-interval.ms, 1000);
But it has no apparent effect. Still
Setting the following two properties may solve your problem.
yarn.resourcemanager.connect.max-wait.ms controls Maximum time to wait to
establish connection to ResourceManager.
yarn.resourcemanager.connect.retry-interval.ms controls How often to try
connecting to the ResourceManager.
Jian
On
@hadoop.apache.org
Subject: Re: very long timeout on failed RM connect
Setting the following two properties may solve your problem.
yarn.resourcemanager.connect.max-wait.mshttp://yarn.resourcemanager.connect.max-wait.ms/
controls Maximum time to wait to establish connection to ResourceManager