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

Robert Kanter commented on OOZIE-1616:
--------------------------------------

Ok, then I'll wait on updating this patch until after OOZIE-1519 is in.  I 
thought that the Instrumentation stuff repopulated all of its values every 
minute, but it looks like it doesn't for "variables".  I can add an 
{{updateVariable(...)}} method to do that.

{quote}
Another general question - how does the instrumentation show up in HA mode for 
different oozie servers?
{quote}
Each server has its own Instrumentation, which makes sense because they may not 
be homogeneous (e.g. different amounts of Memory).  If the user is accessing 
Oozie through a load balancer, or some other round-robin thing, then every time 
they refresh the page, they will possibly hit a different Oozie server and see 
differences in the instrumentation info in the UI.  I think that's fine because 
its really more of an admin thing and if someone is really interested in these 
values they would be interested in a specific Oozie server and can just go to 
that server directly instead of through the load balancer.  Alternatively, we 
could try to have a way of displaying subtabs (one for each server) on the UI 
and have the REST command return an array of servers and their instrumentation 
info.  

> Add sharelib and launcherlib locations to the instrumentation info
> ------------------------------------------------------------------
>
>                 Key: OOZIE-1616
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1616
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: OOZIE-1616.patch
>
>
> It would be convenient to add the sharelib and launcher lib locations to the 
> instrumentation info reported by Oozie.  This way, users can easily see which 
> sharelib they are currently using.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to