New Features in Cloudera Manager 6.0.0

You can now access the Cloudera Manager Swagger API user interface through the Cloudera Manager Admin Console. Navigate to Support > API Explorer to open Swagger.

Cloudera Manager 6.0 introduces new Python and Java API clients based on the Swagger API. These new API clients support all Cloudera Manager API versions.

Compatibility with Older Versions

The Older Python client Older Java client are still supported when the API version is lower than 30. Therefore, older Python and Java API clients can still be used with Cloudera Manager version 6.0 and higher as long as API version 19 or lower is used.

For example, a customer can use old Cloudera Manager API client version 5.14 with Cloudera Manager version 6.0, which by default invokes API version 19. If a customer wants to use new features that were introduced in Cloudera Manager 6.0, (API version 30) then customer must use the new API clients.

Older Python and Java clients and new Swagger-based Python and Java clients can co-exist in an application to allow for incremental transition to new the Swagger-based Python and Java clients.

Auto-TLS simplifies configuring TLS for clusters managed by Cloudera Manager. Cloudera Manager can now add hosts with TLS certificates automatically generated. Additionally, when you add new CDH services, Cloudera Manager populates the TLS configuration for the service.

You can use self-signed certificates created by Cloudera Manager's internal certificate authority, or you can use certificates you already have from a trusted public CA or your own internal CA.

An Enterprise or Trial license is required to enable Auto-TLS.

For more information, see Configuring TLS Encryption for Cloudera Manager and CDH Using Auto-TLS.

You can now assign privileges for specific clusters to the following user roles: Cluster Administrator, Operator, Limited Operator, Configurator, and Read-Only.

For example, the user account lucy has the Cluster Administrator role with privileges for a cluster named Cluster1. lucy can only perform the Cluster Administrator actions on Cluster1. She cannot perform actions on any other cluster managed by Cloudera Manager.

For more information, see Cloudera Manager User Roles.

• CSDs can now specify more than one repository for parcels. A list of URLs can be specified via the new property additionalRepoUrls of the parcel descriptor.
• CSD authors can declare a set of invalid values for numeric parameters for the following types: long, double, port, and memory.

New command to create the HBase HDFS WAL directory in a separate location. By default the HBase HDFS WAL directory is created in /hbase/WALs. New command allows the HBase HDFS WAL directory to be created a different location. After setting the separate WAL directory, the Hbase service needs to be restarted.

Cloudera Manager now passes SSL keystore credentials to SOLR through the Hadoop Credential Store.

• The performance for the cluster status table loading time on the Cloudera Manager Admin Console home page for large clusters has been improved.
• The cluster restart command/operation can be retried now. This is especially helpful in a large cluster where the user has an opportunity to fix the cluster restart failure and retry the failed command.
• When Cloudera Manager sees multiple agents with the same hostname or IP appearing, it will ask users to adjust the UUID on the host and remove the agent that has no roles running.

Cloudera Manager has the following upgrade improvements:

• New upgrade wizard and documentation.

  The Cloudera Enterprise Upgrade Guide allows you to create a customized version of the guide that only includes the steps required for your upgrade. You can use a form at the top of pages in the guide to select your Cloudera Enterprise versions, operating system versions, databases, and other information about your upgrade. The information you enter is retained on each page in the guide.

• You can now run the Host and Service inspectors up to two days prior to an upgrade. This allows a long running inspection to complete prior to starting the upgrade.
• Rolling upgrades for CDH have been improved. YARN jobs running MapReduce2 are now configured to read MapReduce JARs from HDFS instead of from local disk. This makes jobs more robust during rolling upgrade when the local binaries are modified while a job is executing. Clusters created in or upgrading to CDH 6.0 will use this new behavior.

Because of changes to Cloudera Manager, the commands used for a hard stop and hard restart have changed.

For more information, see Starting, Stopping, and Restarting Cloudera Manager Agents.

The hiverserver2_load_balancer change affects Hive services when HiveServer 2 is configured for High Availability.

The hdfs_client_java_opts parameter configures the Client Java Configuration Options, found under the HDFS Gateway role configuration.

The other parameters tune the behavior of health test checking for the HBase Master, HDFS NameNode, MapReduce JobTracker, and YARN ResourceManager respectively.

Any API scripts or cluster templates referencing the old names will need to be updated to use the new names.

Cloudera Issue: OPSAPS-33266, OPSAPS-39223, and OPSAPS-24569

Downloading the client configuration for a service now requires a user account that meets the following requirements: the user account must be assigned a user role that has permission to perform the action and has privileges for the specific cluster because of the new cluster-specific user role feature.

Previously, Cloudera Manager, by default, mapped specific values from an external authentication method to Cloudera Manager user roles.

For example, if the authentication method for Cloudera Manager is a SAML Script, Cloudera Manager automatically mapped exit codes 0 to 11 to the user roles that Cloudera Manager ships with. If you upgrade to Cloudera Manager 6, these mappings are preserved. You can continue using these default mappings, create additional ones, or map different values.

If you perform a fresh installation of Cloudera Manager, values must be mapped to user roles manually in Cloudera Manager.

Additionally, LDAP Group, SAML Attribute, and External Program to user role mappings are no longer done through the Administration > Settings page. Instead, like the exit codes for SAML Scripts s, they are configured on the new Administration > Users & Roles (previously Users) > <Authentication Method> page.

For more information, see Mapping External Authentication to a Role.

• Updated property values:
  Updated the default values for the following properties to match the upstream defaults:

  • hbase.snapshot.region.timeout
  • hbase.snapshot.master.timeout.millis
  • hbase.client.retries.number (all roles)
  • hbase.hstore.blockingStoreFiles (regionserver)
  Removed the following values:

  • hbase.snapshot.master.timeoutMillis
  • hbase.fs.tmp.dir (all roles)
  • hbase.bucketcache.combinedcache.enabled (regionserver)
  • hbase.bulkload.staging.dir (regionserver)
  • hbase.regionserver.hlog.blocksize (regionserver)
• The HBase Thrift Server now turns on Framed Transport and Compact Protocols by default out of the box for safety reasons. This may require code changes to any custom client-side thrift programs that connect to the HBase Thrift Server to continue working.

The following list describes changes to menu names:

• Users

  The Users page that is accessed from the Administration menu has been renamed to Users & Roles.

If you create a user and do not assign a role to it, the user defaults to no access. The user cannot perform any actions on the cluster.

The default HDFS block count reporting threshold for Cloudera Manager has been changed to 1000000 from 500000. When you upgrade, the configuration will be updated to the new default if you are using the default.

The Dashboard and Auditor user roles can now view the Solr Collection Statistics and the HBase Table Statistics pages.