- 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-12-2016 10:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Ian,
Yes, to anyone experiencing the same behavior and looking for the solution, we simply needed to change the permissions on /mr-history in HDFS. Upgrading the timeline server to 1.5 was not necessary (and I couldn't get it to work).

- « Previous
- Next »