Re: what happens to a client attempting to get a new app when the resource manager is already down

2014-02-05 Thread Vinod Kumar Vavilapalli
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 trying to solve a problem. My client run as a server. And was trying to 
 make my client aware about the fact the resource manager is down but I could 
 not figure out. The reason is that the call :  
 yarnClient.createApplication(); never return when the resource manager is 
 down. However it just stay in a loops and sleep after 10 iteration and 
 continue the same loops. Below you can find the logs. Any idea how to leave 
 this loop ? is there any parameter that control the number of seconds before 
 giving up.
 
 Thanks
 
 Reyane OUKPEDJO
 
 
 
 
 
 
 
 logs
 14/01/31 10:48:05 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:06 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:37 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:38 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:39 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:40 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:41 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:42 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:43 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 6 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:44 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 7 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:45 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:46 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:17 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:18 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:19 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:20 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:21 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:22 INFO ipc.Client: Retrying connect to server: 
 isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy is 
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, 

RE: what happens to a client attempting to get a new app when the resource manager is already down

2014-02-05 Thread Rohith Sharma K S
   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 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 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.commailto:r.oukpe...@yahoo.com wrote:


Hi there,

I am trying to solve a problem. My client run as a server. And was trying to 
make my client aware about the fact the resource manager is down but I could 
not figure out. The reason is that the call :  yarnClient.createApplication(); 
never return when the resource manager is down. However it just stay in a loops 
and sleep after 10 iteration and continue the same loops. Below you can find 
the logs. Any idea how to leave this loop ? is there any parameter that control 
the number of seconds before giving up.

Thanks

Reyane OUKPEDJO







logs
14/01/31 10:48:05 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:06 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:37 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:38 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:39 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:40 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:41 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:42 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:43 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 6 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:44 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 7 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:45 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:46 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:17 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:18 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:19 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:20 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:21 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:22 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy 

Re: what happens to a client attempting to get a new app when the resource manager is already down

2014-02-04 Thread REYANE OUKPEDJO
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 at 10:52 PM, REYANE OUKPEDJO r.oukpe...@yahoo.com wrote:

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 
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-interval.ms controls How often to try 
connecting to the ResourceManager.


Jian 



On Fri, Jan 31, 2014 at 11:52 PM, REYANE OUKPEDJO r.oukpe...@yahoo.com wrote:

Hi there,


I am trying to solve a problem. My client run as a server. And was trying to 
make my client aware about the fact the resource manager is down but I could 
not figure out. The reason is that the call :  
yarnClient.createApplication(); never return when the resource manager is 
down. However it just stay in a loops and sleep after 10 iteration and 
continue the same loops. Below you can find the logs. Any idea how to leave 
this loop ? is there any parameter that control the number of seconds before 
giving up.


Thanks


Reyane OUKPEDJO














logs
14/01/31 10:48:05 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:06 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:37 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:38 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:39 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:40 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:41 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:42 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:43 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 6 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:44 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 7 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:45 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:46 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:17 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:18 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:19 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:20 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:21 INFO ipc.Client: Retrying connect to server: 

Re: what happens to a client attempting to get a new app when the resource manager is already down

2014-02-03 Thread REYANE OUKPEDJO
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 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-interval.ms controls How often to try 
connecting to the ResourceManager.

Jian 



On Fri, Jan 31, 2014 at 11:52 PM, REYANE OUKPEDJO r.oukpe...@yahoo.com wrote:

Hi there,


I am trying to solve a problem. My client run as a server. And was trying to 
make my client aware about the fact the resource manager is down but I could 
not figure out. The reason is that the call :  yarnClient.createApplication(); 
never return when the resource manager is down. However it just stay in a 
loops and sleep after 10 iteration and continue the same loops. Below you can 
find the logs. Any idea how to leave this loop ? is there any parameter that 
control the number of seconds before giving up.


Thanks


Reyane OUKPEDJO














logs
14/01/31 10:48:05 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:06 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:37 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:38 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:39 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:40 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:41 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:42 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:43 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 6 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:44 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 7 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:45 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 8 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:48:46 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 9 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:17 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 0 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:18 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 1 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:19 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 2 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:20 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 3 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:21 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 4 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
14/01/31 10:49:22 INFO ipc.Client: Retrying connect to server: 
isblade2/9.32.160.125:8032. Already tried 5 time(s); retry policy is 
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)



CONFIDENTIALITY NOTICE
NOTICE: 

Re: what happens to a client attempting to get a new app when the resource manager is already down

2014-02-03 Thread Jian He
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 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 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-interval.ms controls How often to try
 connecting to the ResourceManager.

 Jian


 On Fri, Jan 31, 2014 at 11:52 PM, REYANE OUKPEDJO r.oukpe...@yahoo.comwrote:

 Hi there,

 I am trying to solve a problem. My client run as a server. And was trying
 to make my client aware about the fact the resource manager is down but I
 could not figure out. The reason is that the call :
  yarnClient.createApplication(); never return when the resource manager is
 down. However it just stay in a loops and sleep after 10 iteration and
 continue the same loops. Below you can find the logs. Any idea how to leave
 this loop ? is there any parameter that control the number of seconds
 before giving up.

 Thanks

 Reyane OUKPEDJO







 logs
 14/01/31 10:48:05 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 8 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:06 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 9 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:37 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 0 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:38 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 1 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:39 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 2 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:40 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 3 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:41 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 4 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:42 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 5 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:43 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 6 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:44 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 7 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:45 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 8 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:46 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 9 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:17 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 0 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:18 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 1 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:19 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 2 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:20 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 3 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:21 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 4 time(s); retry policy is
 

Re: what happens to a client attempting to get a new app when the resource manager is already down

2014-02-02 Thread Jian He
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-interval.ms controls How often to try
connecting to the ResourceManager.


Jian


On Fri, Jan 31, 2014 at 11:52 PM, REYANE OUKPEDJO r.oukpe...@yahoo.comwrote:

 Hi there,

 I am trying to solve a problem. My client run as a server. And was trying
 to make my client aware about the fact the resource manager is down but I
 could not figure out. The reason is that the call :
  yarnClient.createApplication(); never return when the resource manager is
 down. However it just stay in a loops and sleep after 10 iteration and
 continue the same loops. Below you can find the logs. Any idea how to leave
 this loop ? is there any parameter that control the number of seconds
 before giving up.

 Thanks

 Reyane OUKPEDJO







 logs
 14/01/31 10:48:05 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 8 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:06 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 9 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:37 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 0 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:38 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 1 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:39 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 2 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:40 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 3 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:41 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 4 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:42 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 5 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:43 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 6 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:44 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 7 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:45 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 8 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:48:46 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 9 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:17 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 0 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:18 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 1 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:19 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 2 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:20 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 3 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:21 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 4 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
 14/01/31 10:49:22 INFO ipc.Client: Retrying connect to server: isblade2/
 9.32.160.125:8032. Already tried 5 time(s); retry policy is
 RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under