Member since
04-15-2019
4
Posts
0
Kudos Received
0
Solutions
11-23-2018
06:50 AM
Please check and share logs : Create a Hive DB / Table and Look for any Exception / Error related to AtlasHook or Kafka Notifications in /var/log/hive/hiveserver2.log Please share the exception to get to root cause.
... View more
11-23-2018
06:30 AM
Yes, it might be due to both the reasons. Policy with same name or policy exists for same resource. If you want to override policies in target cluster's service, you can use override=true
... View more
06-28-2018
04:03 AM
@Abhilash : Please refer to REST API documentation for Service REST : https://ranger.apache.org/apidocs/resource_ServiceREST.html#resource_ServiceREST_createPolicy_POST
... View more
11-21-2016
02:25 PM
Known issue : There is a known issue with this configuration. When Ranger service is installed using custom user (Service user’s name can be updated during installation of a service on a Misc Tab on Ambari) and location of PID file was changed by the user (i.e. value of below given property is changed from its default.), there is an issue with service startup. On Ambari Configs section of Ranger :
ranger-env / ranger_pid_dir = /var/run/ranger ## is a default value If user changes value of the above property to be a different folder, there is an issue with usersync service startup. When usersync start command is called, it invokes /grid/0/hdp/<version>/ranger-usersync/ranger-usersync-services.sh script, which has hardcoded value of PID file for usersync process and the owner as ‘ranger’. Because of this, usersync restart will fail as custom service user does not have permission to create or write pid file on the directory owned by user ‘ranger’. Workaround In order to solve above issue of usersync startup /grid/0/hdp/<version>/ranger-usersync/ranger-usersync-services.sh needs to be updated to reflect the non-default values. Edit ranger-usersync-services.sh Provide correct path for :: pidf And change chown command giving access to the custom user used in the implementation. Once these changes are done in ranger-usersync-services.sh file, restart Ranger services from Ambari. This issue has been resolved as part of HDP-2.6, however if anyone observes same issue in earlier version, this article could be helpful.
... View more