Dear Cloudera Manager users,
We are pleased to announce the release of Cloudera Manager 5.1.1 and 4.8.4. These are maintenance releases and have a number of bug fixes.
Directory quota in Cloudera Manager shows incorrect values.
Activity Monitor in Cloudera Manager doesn't request new http service ticket.
Many Hive replications running at the same time can cause some of them to fail with "Read timed out" errors.
Multiple Hive replications running at the same time can cause some of them to fail with "command succeeded, but unable to fetch results" errors. This has been noted to occur with as few as 20 replications.
Multiple Hive replications started at exactly the same time (typically triggered by replication schedules) can cause one or more of them to complete successfully without actually replicating the desired metadata.
Replications can be affected by other replications or commands running at the same time.
For more details, see the Cloudera Manager 4.8.4 release notes: http://www.cloudera.com/content/cloudera-content/cloudera-docs/Cloudera Manager4Ent/latest/Cloudera-...
All of the Cloudera Manager 4.8.4 documentation can be found here:
Add/Upgrade Hosts wizards install incorrect JCE policy files if Java 7 is already installed on RPM based distros.
For more details, see the Cloudera Manager 5.1.1 release notes: http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Release-N...
All of the Cloudera Manager 5.1.1 documentation can be found here:
You can download this latest Cloudera Manager here or you can upgrade from an existing installation of Cloudera Manager. Installation and upgrade documentation can be found here for Cloudera Manager 4.8.4 and here for Cloudera Manager 5.1.1.