Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Any article for symlinks

Any article for symlinks

Mostly symlinks issues are fixed as we face them by comparing existing working setup etc, but is there is any design document which explains the larger symlink layout in Ambari which can be referred / passed on to customer ? This issue becomes crucial during upgrades . Also should be able to explain the directories such as "conf.empty" and CLASSPATH requirements etc.

4 REPLIES 4
Highlighted

Re: Any article for symlinks

Contributor

Re: Any article for symlinks

Super Collaborator

That's a well-written article. Overall, the way that you should think of it is like this:

  • /etc/<component>/conf is legacy and used mainly by administrators and some hard-coded scripts
  • /usr/hdp/current/<component>/conf is used by Ambari and most scripts and points to the versioned configuration directory
  • /etc/<component>/<version>/0 is the actual location of the configs

Here's an example using HiveServer2:

/etc/hive/conf -> /usr/hdp/current/hive-server2/conf
/usr/hdp/current/hive-server2/conf -> /etc/hive/2.4.2.0-236/0

Ambari actually moves symlinks around after installation of RPM to make it look like the above. The raw installation packages don't have it like this; we change it in order to support parallel configurations in mixed-version clusters.

Re: Any article for symlinks

thanks a lot

Re: Any article for symlinks

Thanks. Its an informative article.