You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/12/12 21:25:07 UTC

[jira] [Commented] (OOZIE-1616) Add sharelib and launcherlib locations to the instrumentation info

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

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

{quote}
But you will have to modify this patch to update the value of sharelib.location when admin command is issued.
{quote}
I just took a look at {{Instrumentation.java}} and it looks like it will get the new value whenever it updates itself (i.e. the value is "live").  However, it will update only once the Instrumentation updates, which defaults to every minute; so there may be a delay of up to a minute, but I think that's okay.

But I'll update the patch to get the sharelib path like the CLI/REST API does

> 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: Sub-task
>    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.4#6159)