[jira] [Updated] (OOZIE-1676) Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

["Robert Kanter (JIRA)" <ji...@apache.org>]

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

Robert Kanter updated OOZIE-1676:
---------------------------------

    Attachment: OOZIE-1676.patch

The patch adds a v3 of the API.  Only the admin servlet is currently any different though (the other v2 servlets are re-used for v3 addresses).  

For the Configuration, Java System Properties, and OS Env, the Web UI lists them each in a table.  I thought about a few ideas on how to display this for multiple servers and decided that the best way was to simply add a "Server" column to the table with the Oozie Instance ID.  This also means that if you sort by "Name", then you can easily compare the same property name against the different servers, which can be useful.  Otherwise, it's sorted by "Server" by default, so all properties of a given server are next to each other.

For the Instrumentation, the Web UI lists it in a tree.  The way to display this was more obvious, and I simply added another level in the tree with the Oozie Instance ID.  

The REST API for these commands follows the same way we've been doing with HA where we have the "allservers=false" parameter.  The result back looks like it did in the v2 API, except that there's another level with the Oozie Instance IDs mapping to the data.

I've verified this in an actual cluster with and without HA enabled and everything works fine.  I also added some unit tests.  We weren't specifying the Oozie Instance ID system property during all the tests (only the ZK tests), so I moved that as it's now a normally required System Property; this required some minor additional refactoring.  


> 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
>         Attachments: OOZIE-1676.patch
>
>
> 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.2#6252)