Hi
All entities including NM and client etc. use the same RMProxy to talk with
RM. The retry behavior is controlled by the following two configs.
yarn.resourcemanager.connect.max-wait.ms controls Maximum time to wait to
establish connection to ResourceManager.
yarn.resourcemanager.connect.retry-
Thank you very much.
One last question: Do you think those parameters setting require restarting the
cluster?
Thanks
Reyane OUKPEDJO
On Sunday, February 2, 2014 11:06 AM, Jian He wrote:
Hi
All entities including NM and client etc. use the same RMProxy to talk with RM.
The retry behavi
For NMs talking with RM, you need to restart the NMs to take the configs
into effect.
For the client talking with RM, you don't need to restart the RM.
Jian
On Mon, Feb 3, 2014 at 10:52 PM, REYANE OUKPEDJO wrote:
> Thank you very much.
> One last question: Do you think those parameters setting
Thank you very much.
Reyane OUKPEDJO
On Monday, February 3, 2014 10:28 AM, Jian He wrote:
For NMs talking with RM, you need to restart the NMs to take the configs into
effect.
For the client talking with RM, you don't need to restart the RM.
Jian
On Mon, Feb 3, 2014 at 10:52 PM, REYANE
Is this on trunk or a released version?
I think the default behavior (when RM HA is not enabled) shouldn't have client
loop forever. Let me know and we can see if this needs fixing.
Thanks,
+vinod
On Jan 31, 2014, at 7:52 AM, REYANE OUKPEDJO wrote:
> Hi there,
>
> I am trying to solve a pr
half Of
Vinod Kumar Vavilapalli
Sent: 05 February 2014 22:43
To: user@hadoop.apache.org; REYANE OUKPEDJO
Subject: Re: what happens to a client attempting to get a new app when the
resource manager is already down
Is this on trunk or a released version?
I think the default behavior (when RM HA
