hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arun Suresh <asur...@apache.org>
Subject Re: [YARN-6483] Add nodes transitioning to DECOMMISSIONING state to the list of updated nodes returned by the Resource Manager as a response to the Application Master heartbeat
Date Wed, 15 Nov 2017 18:28:16 GMT
Hello Juan

Will take a look at it. Lets continue discussion on the JIRA

Cheers
-Arun

On Wed, Nov 15, 2017 at 10:25 AM, Juan Rodríguez Hortalá <
juan.rodriguez.hortala@gmail.com> wrote:

> Hi,
>
> Does someone have any thoughts on this proposal?
>
> Thanks,
>
> Juan
>
> On Sun, Nov 12, 2017 at 5:27 PM, Juan Rodríguez Hortalá <
> juan.rodriguez.hortala@gmail.com> wrote:
>
> > Hi,
> >
> > I have submitted a pull request https://github.com/apache/
> hadoop/pull/289
> >  for https://issues.apache.org/jira/browse/YARN-6483. This change is an
> > alternative proposal to YARN-3224, for notifying application masters
> > about the decommission of a node, that could help completing
> > https://issues.apache.org/jira/browse/YARN-914. This could be useful for
> > implementing functionality like for example
> https://github.com/apache/spar
> > k/pull/19267, where a Spark AM is able to blacklist executors when their
> > corresponding node transitions into DECOMMISSIONING state.
> >
> > I would like to hear your feedback on this.
> >
> > Thanks,
> >
> > Juan Rodriguez Hortala
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message