[
https://issues.apache.org/jira/browse/AMBARI-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-6533:
----------------------------------------
Attachment: patch_bug-12992.txt
Patch
> Add API to get file log location in the task execution output, currently
> hardcoded in UI
> ----------------------------------------------------------------------------------------
>
> Key: AMBARI-6533
> URL: https://issues.apache.org/jira/browse/AMBARI-6533
> Project: Ambari
> Issue Type: Task
> Components: site
> Affects Versions: 1.6.1
> Reporter: Alejandro Fernandez
> Fix For: 1.7.0
>
> Attachments: patch_bug-12992.txt
>
>
> The Task Execution Output window hardcodes the path to the log files (stdout
> and stderr). Because the prefix path is configured for each agent in
> ambari-agent.ini, it's possible for each agent to have its own independent
> value, and if the configuration changes, then historic logs will not be
> referenced correctly.
> The ask is to remove the hardcoded prefix from the UI, retrieve the log file
> paths by calling an API, and store the log file path for each task.
> Related item:
> Once we have the API available, it would be possible to display the logs via
> an HTTP server running on the agents.
> Proposal:
> The agent will advertise its prefix path when it registers, and the server
> will store the path for each host in-memory.
> When the server spawns a task execution on an agent, it will insert a record
> into the host_command_role table, which will contain 2 new fields to store
> the values for output_log and error_log, by retrieving the prefix path for
> the host that the command will run on.
> Then, the UI can simply query the API to display the log paths.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
