Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <482317014.1207567344314.JavaMail.jira@brutus>
Date: Mon, 7 Apr 2008 04:22:24 -0700 (PDT)
From: "Subramaniam Krishnan (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3171) speculative execution should not
 have default value on hadoop-default.xml bundled in the Hadoop JAR
In-Reply-To: <1831374208.1207315044390.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586335#action_12586335 ] 

Subramaniam Krishnan commented on HADOOP-3171:
----------------------------------------------

I think a simpler solution would be that the Job Client does NOT load the hadoop-default.xml , instead it only loads the hadoop-site.xml if it's present.
This way, only the default values on Server side take effect.

> 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
>             Fix For: 0.17.0
>
>
> 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.