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 r.oukpe...@yahoo.com wrote:
Hi there,
I am
Default Retry time period is 15 minutes. Setting configuration
yarn.resourcemanager.connect.max-wait.ms to lesser value, retry period can
be reduced in client side.
Thanks Regards
Rohith Sharma K S
From: Vinod Kumar Vavilapalli [mailto:vino...@hortonworks.com] On Behalf Of
Vinod
Thank you very much.
Reyane OUKPEDJO
On Monday, February 3, 2014 10:28 AM, Jian He j...@hortonworks.com 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
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 j...@hortonworks.com wrote:
Hi
All entities including NM and client etc. use the same RMProxy to talk with
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 r.oukpe...@yahoo.comwrote:
Thank you very much.
One last question: Do you think those
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.
