Known Issues Fixed in Cloudera Manager 4.8.2
Cloudera Manager doesn't always correctly restart services
In order to deploy this fix, you must hard restart all Cloudera Manager Agents, which requires that you stop all services. You can wait for a convenient time stop all cluster services; services will continue to run in the meantime, but the fix for the defect won't take effect until you perform these steps:
- Stop all services, including the Cloudera management service.
- On all hosts with Cloudera Manager Agents, run this command:
$ sudo service cloudera-scm-agent hard_restart
- Restart all services.
UI performance optimizations when managing large clusters
- Improved the performance of the All Hosts and Parcels pages when there are a large number of clusters
- Made the cluster ordering consistent throughout the UI
Cloudera Manager now displays the patch number in the parcel release information
Error messages no longer include special characters that cannot be displayed in a browser
Federated Namespace UI no longer throws error
When you selecton a nameservice, the Cloudera Manager Admin Console no longer displays a JsonMappingException.