You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2012/11/13 02:48:12 UTC

[jira] [Updated] (OOZIE-1015) HadoopAccessorService jobtracker validation should not have hardcoded conf key

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

Mona Chitnis updated OOZIE-1015:
--------------------------------

    Attachment: OOZIE-1015v2.patch

Incorporated Harsh's comments
                
> HadoopAccessorService jobtracker validation should not have hardcoded conf key
> ------------------------------------------------------------------------------
>
>                 Key: OOZIE-1015
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1015
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>             Fix For: trunk
>
>         Attachments: OOZIE-1015.patch, OOZIE-1015v2.patch
>
>
> While validating the jobtracker address against whitelist in HadoopAccessorService, the conf key to be looked up is a string value "mapred.job.tracker". Instead we should use static variables for robustness (mapred.job.tracker for hadoop-1 and yarn.resourcemanager.address for hadoop-2)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira