Fixed Issues in Cloudera Manager 6.1.1

The following sections describes issues fixed in Cloudera Manager 6.1.1:

Backup and disaster recovery (BDR) HDFS and Hive replications will fail on clusters running Cloudera Manager 6.1.0

This issue caused BDR HDFS and Hive replications to fail when you replicated from secured (Kerberized) source clusters to destination clusters that have been upgraded to Cloudera Manager 6.1.0.

This issue has been fixed in this release. After upgrade, the schedules will correctly identify the source as either a secure or unsecure cluster. In the case of multiple peers, one secure and another unsecure peer is supported.

Cloudera Issue: OPSAPS-48865

The Add Hosts link on the Cloudera Director page is broken in the public cloud scenario

When you add hosts to Cloudera Manager deployed in AWS, a page that describes Cloudera Director is displayed. There is a link to the classic Add Hosts wizard. This wizard was broken in version 6.0.0 and 6.0.1. This issue is fixed in this release.

Cloudera Issue: OPSAPS-48627

BDR fails if dfs.nameservices is overridden with multiple nameservice names

This fix:

1. Adds a feature flag that you can use to disable the replace nameservice feature by calling the following API call: 
http://cm_host:cm_port/api/v19/cm/config
with the body: 
{"items":[{"name":"feature_flag_bdr_replace_nameservice","value":"false"}]}

2. Handles the scenario for multiple nameservices in dfs.nameservices configuration. Now the feature cross-checks that with the fs.defaultFS configured in core-site.xml.

Cloudera Issue: OPSAPS-48579

The diff format is not displayed on the configuration revisions diff page

The delta between the old and the new configuration value was previously shown using a red background color to indicate removal, and a green color to indicate addition. This was not displaying correctly in Cloudera Manager 6.1.0. This issue is fixed in this release.

Cloudera Issue: OPSAPS-48544

Decommissioning a DataNode during a current decommission (in parallel) never completes

With this change, you can decommission DataNodes in parallel. They won't appear to be stuck as incomplete on the user interface.

Cloudera Issue: OPSAPS-39746