[
https://issues.apache.org/jira/browse/MAPREDUCE-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-6315:
-----------------------------------------------
Target Version/s: 2.9.0 (was: 2.8.0)
I applied the patch and looked at it. {{mapred job -logs}} is an arcane command
that I don't know of a lot of users using. It definitely isn't the first place
our users go - that would be the web UI. Given that, I also agree that putting
this in the JobHistory-UI is a minimum requirement.
Even without that, this patch needs more work as commented above.
Note that YARN's the ResourceManager does have these log-links against each
app-attempt.
Given all of the above, I am moving this into 2.9 and unblocking 2.8.0. Please
revert back if you disagree. Tx.
> Implement retrieval of logs for crashed MR-AM via jhist in the staging
> directory
> --------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6315
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6315
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client, mr-am
> Affects Versions: 2.7.0
> Reporter: Gera Shegalov
> Priority: Critical
> Labels: BB2015-05-TBR
> Attachments: MAPREDUCE-6315.001.patch, MAPREDUCE-6315.002.patch,
> MAPREDUCE-6315.003.patch
>
>
> When all AM attempts crash, there is no record of them in JHS. Thus no easy
> way to get the logs. This JIRA automates the procedure by utilizing the jhist
> file in the staging directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
