You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-user@hadoop.apache.org by Caesar Samsi <ma...@samsi.us> on 2016/02/13 23:48:00 UTC
How to configure detection of failed NodeManager's sooner?
Hello,
From testing it appears detecting a failed NM node takes quite some time (~5 minutes)
Is there a configurable setting for this? I need a more responsive cluster.
Thank you, Caesar.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
For additional commands, e-mail: user-help@hadoop.apache.org
Re: How to configure detection of failed NodeManager's sooner?
Posted by Harsh J <ha...@cloudera.com>.
You're looking for the property
"yarn.nm.liveness-monitor.expiry-interval-ms", whose default is 600000ms
(10m). This is to be set on the ResourceManager(s)' yarn-site.xml.
(X-Ref:
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-common/yarn-default.xml#yarn.nm.liveness-monitor.expiry-interval-ms
)
On Sun, Feb 14, 2016 at 4:18 AM Caesar Samsi <ma...@samsi.us> wrote:
> Hello,
>
> From testing it appears detecting a failed NM node takes quite some time
> (~5 minutes)
>
> Is there a configurable setting for this? I need a more responsive cluster.
>
> Thank you, Caesar.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>
>
Re: How to configure detection of failed NodeManager's sooner?
Posted by Harsh J <ha...@cloudera.com>.
You're looking for the property
"yarn.nm.liveness-monitor.expiry-interval-ms", whose default is 600000ms
(10m). This is to be set on the ResourceManager(s)' yarn-site.xml.
(X-Ref:
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-common/yarn-default.xml#yarn.nm.liveness-monitor.expiry-interval-ms
)
On Sun, Feb 14, 2016 at 4:18 AM Caesar Samsi <ma...@samsi.us> wrote:
> Hello,
>
> From testing it appears detecting a failed NM node takes quite some time
> (~5 minutes)
>
> Is there a configurable setting for this? I need a more responsive cluster.
>
> Thank you, Caesar.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>
>
Re: How to configure detection of failed NodeManager's sooner?
Posted by Harsh J <ha...@cloudera.com>.
You're looking for the property
"yarn.nm.liveness-monitor.expiry-interval-ms", whose default is 600000ms
(10m). This is to be set on the ResourceManager(s)' yarn-site.xml.
(X-Ref:
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-common/yarn-default.xml#yarn.nm.liveness-monitor.expiry-interval-ms
)
On Sun, Feb 14, 2016 at 4:18 AM Caesar Samsi <ma...@samsi.us> wrote:
> Hello,
>
> From testing it appears detecting a failed NM node takes quite some time
> (~5 minutes)
>
> Is there a configurable setting for this? I need a more responsive cluster.
>
> Thank you, Caesar.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>
>
Re: How to configure detection of failed NodeManager's sooner?
Posted by Harsh J <ha...@cloudera.com>.
You're looking for the property
"yarn.nm.liveness-monitor.expiry-interval-ms", whose default is 600000ms
(10m). This is to be set on the ResourceManager(s)' yarn-site.xml.
(X-Ref:
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-common/yarn-default.xml#yarn.nm.liveness-monitor.expiry-interval-ms
)
On Sun, Feb 14, 2016 at 4:18 AM Caesar Samsi <ma...@samsi.us> wrote:
> Hello,
>
> From testing it appears detecting a failed NM node takes quite some time
> (~5 minutes)
>
> Is there a configurable setting for this? I need a more responsive cluster.
>
> Thank you, Caesar.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>
>