hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-3171) speculative execution should not have default value on hadoop-default.xml bundled in the Hadoop JAR
Date Thu, 10 Apr 2008 07:58:06 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Owen O'Malley resolved HADOOP-3171.
-----------------------------------

    Resolution: Won't Fix

-1 on Arun's patch because the first resource is not distinguished as the default resource.
Not saving it in the serialization will lead to confusion and delay.

If a cluster admin wants to force speculation off, they just need to set it off on the job
tracker as a final parameter. This is not a bug, but a configuration problem..

> speculative execution should not have default value on hadoop-default.xml bundled in
the Hadoop JAR
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3171
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3171
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.16.2
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Arun C Murthy
>         Attachments: HADOOP-3171_20080410.patch
>
>
> Having a default value for speculative execution in the hadoop-default.xml bundled in
the Hadoop JAR file does not allow a cluster to control the default behavior. 
> *ON in hadoop-default.xml (current behavior)*
> * ON in JT hadoop-site.xml
>  * present in job.xml, job's value is used
>  * not-present in job.xml, ON is taken as default from the hadoop-default.xml present
in the client's JAR/conf (*)
> * ON FINAL in the JT hadoop-site.xml
>  * present or not present in the job.xml, ON is used
> * OFF in JT hadoop-site.xml
>  * present in job.xml, job's value is used
>  * not-present in job.xml, ON is taken as default from the hadoop-default.xml present
in the client's JAR/conf
> * OF FINAL in the JT hadoop-site.xml
>  * present or not present in the job.xml, OFF is used
> *OFF in hadoop-default.xml (not current behavior)*
> * ON in JT hadoop-site.xml
>  * present in job.xml, job's value is used
>  * not-present in job.xml, OFF is taken as default from the hadoop-default.xml present
in the client's JAR/conf (*)
> * ON FINAL in the JT hadoop-site.xml
>  * present or not present in the job.xml, ON is used
> * OFF in JT hadoop-site.xml
>  * present in job.xml, job's value is used
>  * not-present in job.xml, ON is taken as default from the hadoop-default.xml present
in the client's JAR/conf
> * OF FINAL in the JT hadoop-site.xml
>  * present or not present in the job.xml, OFF is used
> ---
> Still is desirable for the JT to have a default value. To avoid having to support 2 hadoop-default.xml
files, one for the JT and other for the clients, the easiest why is to remove it from the
hadoop-default.xml and have the default value in the code when getting the config property
(thing that may be already happening).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message