[
https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119268#comment-14119268
]
Hadoop QA commented on OOZIE-1676:
----------------------------------
Testing JIRA OOZIE-1676
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 10 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:red}-1{color} patch does not compile
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{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} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
. {color:red}-1{color} distro tarball fails 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/1879/
> Instrumentation and Configuration over the REST API and Web UI should include
> all Oozie servers
> -----------------------------------------------------------------------------------------------
>
> Key: OOZIE-1676
> URL: https://issues.apache.org/jira/browse/OOZIE-1676
> Project: Oozie
> Issue Type: Improvement
> Components: HA
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: 4.1.0
>
> Attachments: OOZIE-1676.patch, OOZIE-1676.patch, OOZIE-1676.patch,
> OOZIE-1676.patch, screenshot.jpg, screenshot2.jpg
>
>
> This isn't that important, but it would be good if we updated the REST API
> and Web UI to return the instrumentation and configuration for each Oozie
> server when HA is being used. As it stands, each time you refresh the page
> (and are going through the load balancer), you'll get the
> instrumentation/configuration for a different server, which are not identical
> and there isn't really a way to tell which server they came from. This
> should be a new version of the REST API (v3) because it would change the
> return format to be an array of servers with their
> instrumentation/configuration info.
> The backend of this would have the contacted Oozie server simply ask each of
> the other Oozie servers for their instrumentation or configuration and
> combine them all (with the name of each server) into the response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
