A bit late to the party, but hope the following will help.   By calling the main functions of the classes,  UnixUserGroupBuilder, PolicyMgrUserGroupBuilder or LdapUserGroupBuilder is not going to work, since the main classes of these are only initializing the classes. In order to start the actual sync, the function updateSink needs to be called. During startup this is handled by the class org.apache.ranger.usergroupsync.UserGroupSync thus, calling its main function will trigger the syncing using the configuration that you set in your cluster.   A complete example for triggering the usersync manually could be: java -Dlogdir=/var/log/ranger/usersync -cp "/usr/hdp/current/ranger-usersync/dist/unixusersync-1.2.0.3.1.5.135-2.jar:/usr/hdp/current/ranger-usersync/lib/*:/etc/ranger/usersync/conf" org.apache.ranger.usergroupsync.UserGroupSync for HDP and java -Dlogdir=/var/log/ranger/usersync -cp "/opt/cloudera/parcels/CDH/lib/ranger-usersync/dist/unixusersync-2.1.7.1.7.0-460.jar:/opt/cloudera/parcels/CDH/lib/ranger-usersync/lib/*:/etc/ranger/usersync/conf" org.apache.ranger.usergroupsync.UserGroupSync for CDP. ... View more

Thanks for the solution!! Same issue for me after enabling MIT Kerberos in the CDH 5.16.2 cluster zookeeper wouldn't start with the above message javax.security.auth.login.LoginException: Message stream modified (41)   I was using openjdk version "1.8.0_272". As per your solution commented the line in /etc/krb5.conf on all servers: #renew_lifetime = 604800       After that restart of cluster all services worked except Hue Kerberos Ticket Renewer which gives error Couldn't renew kerberos ticket in order to work around Kerberos 1.8.1 issue. Please check that the ticket for 'hue/fqdn@KRBREALM' is still renewable: The Kerberos Ticket Renewer is a separate issue and we need to run on the MIT KDC server: kadmin.local:  modprinc -maxrenewlife 90day krbtgt/KRBREALM kadmin.local:  modprinc -maxrenewlife 90day +allow_renewable hue/fqdn@KRBREALM   for all hue servers fqdn   After that  Hue Kerberos Ticket Renewer restarted successfully.   ... View more

Hi @jsensharma , Is there any rest API call available for this recovery host option. That will be very helpful.   Thanks, Bhuban ... View more

Hi, I have a question regarding Cluster version. There are separate nodes for primary and secondary machines, so the cluster version will be same or unique in this scenario? ... View more

You need to find the parent that has the association and delete the references.    Example:  I have a hive table with a column that is SSN and it had two tags associated to it. Even after the association was removed it still contains the history. When you delete you get an error message. Given type {TagName} has references.   In this case I know I have a hive_column that had this reference and I need to find the proper GUID in order to delete this reference and get this test setup out of my UI.    First I do a search for these items above in the Atlas UI.  Check the option for Show historical entities in the event yours has been deleted. The information is displayed in the UI and this is the one I am after. Next I will use the developer tools in chrome and generally I clear out any of the history to help reduce any confusion as to what I am looking for.  Next click on ssn or your entity that was associated to a classification.  The url is in the panel for the get request, and the GUID in the URL is what you are after.   Delete the classification from the GUID. curl -iv -u tkreutzer \ -X DELETE  http://yourhost:21000/api/atlas/v2/entity/guid/ec8a34c7-db67-41b8-a14c-32a19d2166bf/classification/SSNHR   Now you can delete the Classification from the UI, barring there are no other associations. If so, rinse and repeat for each hive column.    I will probably try to figure out a way to do this via REST with Python later in a way that finds all associated GUID's for us.    Hope this help... Cheers          ... View more

Thanks, @Jay Kumar SenSharma ... View more

Thanks, @Jay Kumar SenSharma! ... View more

You're Welcome. I am unsure of the JIRA for which the change has been made, I believe it is https://issues.apache.org/jira/browse/RANGER-2004, https://issues.apache.org/jira/browse/ATLAS-2459 Having said that, I have tested in my lab env with 3.0 and it works 🙂 ... View more

Thank you very much, @Karthik Palanisamy That link is also very helpful. ... View more

Thank you for your detailed comment! ... View more