Hi,
> From my work on yarn trying to document the configs there and to
standardize them, writing anything that is going to automatically detect
config values through static analysis is going to be very difficult. This
is because most of the configs in yarn are now built up using static string
conc
I've seen Oozie do that same break-up of config param names and boy, its
difficult to grep in such a code base when troubleshooting.
OTOH, we at least get a sane prefix for relevant config names (hope we do?)
On 06-Dec-2011, at 12:44 AM, Robert Evans wrote:
> From my work on yarn trying to docu
>From my work on yarn trying to document the configs there and to standardize
>them, writing anything that is going to automatically detect config values
>through static analysis is going to be very difficult. This is because most
>of the configs in yarn are now built up using static string con
Praveen,
(Inline.)
On 05-Dec-2011, at 10:14 PM, Praveen Sripati wrote:
> Hi,
>
> Recently there was a query about the Hadoop framework being tolerant for
> map/reduce task failure towards the job completion. And the solution was to
> set the 'mapreduce.map.failures.maxpercent` and
> 'mapreduce.
working on something similar? If yes, it nice or else I
am willing to spend sometime on this activity. Would appreciate response.
[1]
http://www.cloudera.com/blog/2011/08/automatically-documenting-apache-hadoop-configuration/<http://www.cloudera.com/blog/2011/08/automatically-documenting-apac
