- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Workaround for log aggregation bug
- Labels:
-
Apache Ambari
Created ‎02-10-2016 03:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have log aggregation enabled in the Yarn configuration for our cluster (yarn.log-aggregation-enable).
But it doesn't seem to work.
When I try to drill into the history of a job in the resource manager GUI, the link for "logs" always takes me to a page that says: "aggregation is not enabled".
I've opened a ticket asking for help on this, and they told us we need to upgrade, so we did, but it didn't help.
I opened another ticket and am currently waiting for a response.
In the meantime, has anyone seen this?
Is there is a known hack to fix it?
Any advice about where to look for the solution?
We're currently on 2.2.8
Created ‎02-11-2016 06:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Zack Riesland , thanks for looking at this with me over webex. It turns out it was the ownership of the mr-history directory that was causing aggregation to not work on the web side, this needed to be owned by mapred and hdfs. The initial failure to start was due to that incorrect class which we fixed.
Created ‎02-10-2016 03:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you follow this doc? https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.2/bk_yarn_resource_mgt/content/ch_log_aggrega...
this should also give you some info http://hortonworks.com/blog/simplifying-user-logs-management-and-access-in-yarn/
Created ‎02-10-2016 03:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. It basically just says to set two config properties, which I did.
Created ‎02-10-2016 04:14 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I remember having this issue until I configured TimeLine Server. @Zack Riesland
Created ‎02-10-2016 04:16 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Created ‎02-10-2016 04:21 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Artem,
Yes, this all seems to be setup correctly. I believe we had to tackle this a while back to get the Tez View working.
Created ‎02-10-2016 04:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And you migrated to 1.5 of TS? @Zack Riesland
Created ‎02-10-2016 04:26 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not explicitly specifying yarn.timeline-service.version, so I guess I'm running whatever the 2.2.8 default is.
Do you think I'll have better luck if I upgrade?
Created ‎02-10-2016 04:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would either wait for support or try in dev cluster. @Zack Riesland
Created ‎02-10-2016 04:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please see this thread https://community.hortonworks.com/questions/4719/yarn-logs-seems-to-be-truncated.html
I am afraid that you may not find something really useful. Please followup with the support suggestion.
