[
https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1676:
---------------------------------
Fix Version/s: (was: 4.1.0)
trunk
Ok, I've changed the fix version to trunk.
In any case, I'm now wondering if the Oozie client shouldn't just stick to v2
until we actually change something that it uses (the client doesn't ever call
for Instrumentation or Configuration anyway).
> 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: trunk
>
> 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)
