The "local resources" you mentioned is the exact solution for this. For each
LocalResource, you also mention a LocalResourceVisibility which takes one of
the three values today - PUBLIC, PRIVATE and APPLICATON.
PUBLIC resources are downloaded only once and shared by any application running
on
AM
To: user@hadoop.apache.org
Subject: Re: Distribution of native executables and data for YARN-based
execution
The "local resources" you mentioned is the exact solution for this. For each
LocalResource, you also mention a LocalResourceVisibility which takes one of
the three va
[mailto:vino...@hortonworks.com]
> Sent: Friday, May 17, 2013 12:56 AM
> To: user@hadoop.apache.org
> Subject: Re: Distribution of native executables and data for YARN-based
> execution
> The "local resources" you mentioned is the exact solution for this. For each
> Local
che.org
> Subject: Re: Distribution of native executables and data for YARN-based
> execution
>
>
> The "local resources" you mentioned is the exact solution for this. For each
> LocalResource, you also mention a LocalResourceVisibility which takes one of
> the
gt;
> Cheers,
> Tim
>
>
> From: "John Lilley"
> To: user@hadoop.apache.org
> Sent: Friday, May 17, 2013 8:35:53 AM
> Subject: RE: Distribution of native executables and data for YARN-based
> execution
>
> Thanks! This sounds exactly like what I nee
AM
To: user@hadoop.apache.org
Subject: Re: Distribution of native executables and data for YARN-based
execution
I have a little bit of conflict of interest given I worked on Hadoop YARN all
time but..
I have worked on torque/condor based resource management systems too. There are
many advantag
