Bug 1162364 - yarn/timeline directory cannot be owned by root
Summary: yarn/timeline directory cannot be owned by root
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhs-hadoop-install
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.0.4
Assignee: Jeff Vance
QA Contact: Daniel Horák
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-10 22:59 UTC by Jeff Vance
Modified: 2015-05-13 17:54 UTC (History)
7 users (show)

Fixed In Version: 2.36-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-31 10:18:18 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:0761 0 normal SHIPPED_LIVE Red Hat Storage Server 3 Hadoop plug-in enhancement update 2015-03-31 14:17:20 UTC

Description Jeff Vance 2014-11-10 22:59:53 UTC
Description of problem:
After the ambari wizard installation the /mnt/brick1/hadoop/yarn/ directory is owned by root:root and thus the timeline service cannot start. The owner needs to be yarn:hadoop.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Vance 2014-11-10 23:01:44 UTC
enable_vol.sh fixes the perms and owner of /mnt/brick1/hadoop/yarn and all files under via chown -R and chmod -R.

Comment 5 Daniel Horák 2015-03-13 13:01:42 UTC
When/how/by what should be created directory /mnt/brick1/hadoop/yarn on Master server?

If I'll configure yarn.timeline-service.leveldb-timeline-store.path to point to /mnt/brick1/hadoop/yarn/timeline (as it is in our actual documentation), enabling volume fails with following error:
  DEBUG: update yarn local directories on MASTER (yarn-master)...
  ERROR: chown/chmod local yarn dir "/mnt/brick1/hadoop/yarn": /mnt/brick1/hadoop/yarn missing on MASTER

I think this is related to the bug 1160608.

Our automatic tests were using "/var/log/hadoop-yarn/timeline" as it is suggested in Hortonworks documentation (bug 1160608 comment 0). But now I've check the installation process and correct it accordingly to our documentation and now everything is failing.

So moving this BZ back to ASSIGNED, to evaluate, where should yarn.timeline-service.leveldb-timeline-store.path point. And if /mnt/brick1/hadoop/yarn/timeline is correct location, than evaluate who should create /mnt/brick1/hadoop/yarn directory (or set proper permission on the parent directory).

If it points to /var/log/hadoop-yarn/timeline, the directory /var/log/hadoop-yarn/ is owned by yarn:hadoop (from installation of hadoop-yarn package), so yarn is able to create required timeline files/directories itself.

Comment 6 Jeff Vance 2015-03-17 03:33:45 UTC
Re comment #5: I am unable to duplicate this failure. Can you please paste the /var/log/rhs-hadoop-install.log file showing the entire enable_vol.sh portion?
Note: per my comments #11 in bz 1160608, Ambari creates this directory.

Comment 7 Daniel Horák 2015-03-17 09:24:06 UTC
Jeff, you are right, sorry for false alarm. It was probably some misconfiguration on my site. When I've rerun the tests and check the correct configuration accordingly to Doc, it works properly.

>> MODIFIED

Comment 8 Daniel Horák 2015-03-17 09:24:57 UTC
Tested and VERIFIED on Red Hat Storage Server 3.0 Update 4 with rhs-hadoop-install-2_44-1.el6rhs.noarch.

Ambari correctly created directories /mnt/brick1/hadoop/yarn and enable_vol.sh change the ownership and permissions:

# ll -d /mnt/brick1/hadoop/yarn/
  drwxr-xr-x. 5 yarn hadoop 4096 Mar 17 09:57 /mnt/brick1/hadoop/yarn/

# ll -d /mnt/brick1/hadoop/yarn/timeline/
  drwxr-xr-x. 3 yarn hadoop 4096 Mar 17 09:57 /mnt/brick1/hadoop/yarn/timeline/

>> VERIFIED

Comment 10 errata-xmlrpc 2015-03-31 10:18:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0761.html


Note You need to log in before you can comment on or make changes to this bug.