Fixed Issues in Apache Ranger

Review the list of Ranger issues that are resolved in Cloudera Runtime 7.2.7.

CDPD-16888: Ranger and Atlas services should have recommended heap size configured while deploying a cluster.
Default minimum heap size for Ranger services is now set as 1 GB and for Atlas 2GB. This issue is now resolved.
CDPD-16888: Solr client connection used for communication is not closed and this results in resource leak.
This issue is now resolved.
OPSAPS-58711: ODB cannot deploy against Datalake HA
This issue is now resolved.
CDPD-15401: When you enable Hive Metastore lookup in Ranger admin, resource lookup returns nothing and displays an error.
This issue is now resolved. You must use this step as a solution: sudo
 ln -s /opt/cloudera/parcels/*<CDH-version>*/jars/libfb303-0.9.3.jar
CDPD-14269 and CDPD-14289: Failed resource filtering in Ranger Policy Export.
Exporting tag policies result in a 204 error when the polResource query parameter is used.
CDPD-12848: When you try to create multiple policies using the API having same non-existing group, the group creation fails due to multiple threads trying to create the same group at once.
Separate threads are now created for retry group creation and checks if the group is previously created and associate it with policy.
CDPD-10072: Ranger Ozone plugin unable to write to solr audits in SSL enabled cluster
This issue is now resolved. A separate folder libext is added under the Ozone library path and all the ranger plugin jars are added under this new folder.
OPSAPS-57495: The Ranger role-level principal for Ranger Admin, Ranger Usersync, and Ranger Tagsync can now be customized from the Cloudera Manager UI.