Short Description: Configure Knox to access Atlas UI Article Here is the steps to access Atlas UI through Knox. 1. Make sure Knox is configured properly and it works fine. 2. ssh to Knox gateway host and go to /var/lib/knox/data-2.6.****/services 3. mkdir –p atlas/0.8.0/ mkdir –p atlas-api/0.8.0/ 4. download the configurations from https://github.com/apache/knox/tree/v0.13.0/gateway-service-definitions/src/main/resources/services/atlas-api/0.8.0 URL to /var/lib/knox/data-2.6.***/services/ atlas-api/0.8.0/ 5. download the configurations from https://github.com/apache/knox/tree/v0.13.0/gateway-service-definitions/src/main/resources/services/atlas/0.8.0 URL to /var/lib/knox/data-2.6.***/services/ atlas/0.8.0/ 5. change the owner/Group permissions to Knox for /var/lib/knox/data-2.6.**/services/atlas*/ and subdirectory 6. Go to Knox configurations Modify "Advanced topology" with below service tag <service> <role>ATLAS</role> <url>sandbox.hortonworks.com:21000</url> </service> <service> 7. Restart Knox service. 8. You should be able to access Atlas UI from the below URL https://sandbox.hortonworks.com:8443/gateway/default/atlas/ Please Note: At this point of time, it's a work-around, Hortonworks doesn't support this yet. ... View more

Issue: On Adding Oozie service to cluster, sometimes its possible user could see an error with simple message Failed to create new war file as below and on top of it Oozie server wouldn't start. INFO: Adding extension: /usr/hdp/current/oozie-server/libext/mysql-jdbc-driver.jar Failed: creating new Oozie WAR Solution: Oozie deployment script is trying to unzip the existing Oozie war file and then zip it back up and place it in a sub directory of /tmp/... . This unzip and zip process doubles the storage space required for the Oozie war file. Make sure there is enough /tmp storage for the above process to take place, logs wouldn't provide this info. ... View more