Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1676

Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Patch Available
    • Minor
    • Resolution: Unresolved
    • trunk
    • trunk
    • HA
    • None

    Description

      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.

      Attachments

        1. OOZIE-1676.patch
          79 kB
          Robert Kanter
        2. OOZIE-1676.patch
          77 kB
          Robert Kanter
        3. OOZIE-1676.patch
          76 kB
          Robert Kanter
        4. OOZIE-1676.patch
          54 kB
          Robert Kanter
        5. screenshot.jpg
          79 kB
          Robert Kanter
        6. screenshot2.jpg
          162 kB
          Robert Kanter

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rkanter Robert Kanter
            rkanter Robert Kanter

            Dates

              Created:
              Updated:

              Slack

                Issue deployment