[
https://issues.apache.org/jira/browse/OOZIE-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1616:
---------------------------------
Attachment: OOZIE-1616.patch
I didn't show the entire contents of the sharelib directories (i.e. the jar
files) because that would make the instrumentation output much longer (and
possibly slower); it would also require changes to either allow dynamic keys or
map-structures in the instrumentation variables.
Instead, I added some additional variables that should be helpful and put them
all under a new "libs" group. Here is the output from the instrumentation log:
{noformat}
variables:
…
libs:
launcherlib.system.libpath: /user/rkanter/share/lib/launcher_20131216183917
sharelib.keys: [oozie, hive, distcp, hcatalog, sqoop, mapreduce-streaming,
pig]
sharelib.mapping.file: (none)
sharelib.source: oozie.service.WorkflowAppService.system.libpath
sharelib.system.libpath:
hdfs://localhost:8020/user/rkanter/share/lib/lib_20131216181900
…
{noformat}
Here's a description of the above:
- {{launcherlib.system.libpath}} is the DFS launcher lib dir
- {{sharelib.keys}} is the list of sharelibs
- {{sharelib.mapping.file}} is the mapping file location (it should also be in
the config, but it seemed good to put it here too for completeness)
- {{sharelib.source}} says whether the DFS sharelib dir or the mapping file is
being used currently
- {{sharelib.system.libpath}} is the current DFS share lib dir, including the
timestamp
No tests, but I verified that it shows up in the log, the Web UI, and the REST
API.
> 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, 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)
