Hi @Manoj690    Can you copy - "/var/lib/ambari-server/resources/mysql-connector-java.jar" to "/usr/share/java/" and retry.   Make sure you use correct java path for the java version you are pointing too. ... View more

Hi @laplacesdemon    I agree with you and definately application/third party tools/components must be installed outside cluster or on individual new node to avoid major performance impacts.   Regarding on how to manage the components if the hadoop version changes is pretty kind of devops question i feel. You always need to make some inventory of applications running along with your ecosystem components and their dependencies. Nearby you can use Nexus as centralized repository to fetch new versions which needs to be deployed on your application side[ie. Oracle Data Integrator and Jupyter Hub] with help of jenkins/some deployment tool.   As per my experience i see resource related problems in case you think of installing application on edge nodes. So i will suggest that is not a good idea.   Do revert if you have further points to highlight. ... View more

Hi @Caranthir    Can you try disabling and enabling the plugin again ? While you enable the plugin it adds/modifies below properties - Can you check if those properties are set properly after you enable ranger plugin for hdfs again? Also as already mentioned by @Shelton the repository config user must be configured if you are working in kerberized environment. If still you are not able to see the repository in Ranger UI then you can click on add symbol as shown below to add repository manually - You can specify details of namenode and other and "test connection" Monitor the logs of ranger and namenode while you test connection. If connection fails you can see errors in logs.   Please post for further updates. ... View more

Hi@m4x1m1li4n     Can you confirm -   Are the below ip's defined in /etc/hosts are public or private ipaddress? 13.48.140.49 13.48.181.38 13.48.185.39 13.53.62.160 13.48.18.0 Is the hostname defined in cloudera agent config.ini  seems to be public hostname - "ec2-13-48-140-49.eu-north-1.compute.amazonaws.com" Can you try pointing both /etc/hosts and config.ini[hostname] to private IP within cluster and restart agent. I guess it might be the issue with public DNS.   ... View more