[jira] [Commented] (OOZIE-2187) Add a way to specify a default JT/RM and NN

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621656#comment-14621656 ] 

Hadoop QA commented on OOZIE-2187:
----------------------------------

Testing JIRA OOZIE-2187

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 132
.    {color:green}+1{color} the patch does adds/modifies 6 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:red}-1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:red}-1{color} the patch seems to introduce 2 new javac warning(s)
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1682
.    Tests failed: 2
.    Tests errors: 0

.    The patch failed the following testcases:

.      testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)
.      testStreamingWithMultipleOozieServers_coordActionList(org.apache.oozie.service.TestZKXLogStreamingService)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2435/

> Add a way to specify a default JT/RM and NN
> -------------------------------------------
>
>                 Key: OOZIE-2187
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2187
>             Project: Oozie
>          Issue Type: New Feature
>          Components: core
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: OOZIE-2187.002.patch, OOZIE-2187.003.patch, OOZIE-2187.patch, OOZIE-2187.patch, OOZIE-2187.patch, OOZIE-2187.patch
>
>
> Oozie is cluster agnostic, which is why we require an RM/JT and NN per action in your workflow (or once via the <global> section).  In practice, many users use one Oozie server per cluster, so it's an extra burden for them to have to specify this all the time.  It would be convenient if we added configuration properties to oozie-site that would let you specify a default RM/JT and NN to use.  
> This way, these users could completely omit the {{<job-tracker>}} and {{<name-node>}} fields from their workflows; as an added benefit, they can easily update these values if they ever rename/move their RM/JT or NN.  We'd of course still allow specifying  {{<job-tracker>}} and {{<name-node>}} in each action and {{<global>}} to allow individual workflows or actions to override the default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)