We are pleased to announce the release of the Cloudera Distribution of Apache Kafka 3.0.0 for CDH 5.  Apache Kafka is a highly scalable, distributed, publish-subscribe messaging system.   Cloudera Distribution of Apache Kafka 3.0.0 is a major release based on Apache Kafka 0.11.0.0.   Notable Issues Fixed in Cloudera Distribution of Apache Kafka 3.0.0: [KAFKA-5135] - Controller Health Metrics (KIP-143) [KAFKA-4422] - Drop support for Scala 2.10 (KIP-119) [KAFKA-3995] - Split the ProducerBatch and resend when received RecordTooLargeException [KAFKA-4815] - Idempotent/transactional Producer (KIP-98) [KAFKA-3878] - Exponential backoff for broker reconnect attempts (KIP-144) [KAFKA-4790] - Kafka cannot recover after a disk full All backported fixes can be viewed in the git release notes here or on our website under the Issues fixed section.   We look forward to you trying Kafka 3.0.0. For more information, please use the links below: Install or upgrade Kafka Review the documentation Review the Release Notes   As always, we welcome your feedback. Please send your comments and suggestions through our community forums. ... View more

We are pleased to announce the release of the Cloudera Distribution of Apache Kafka 2.1.2 for CDH 5.  Apache Kafka is a highly scalable, distributed, publish-subscribe messaging system.   Apache Kafka 2.1.2 is maintenance release for Kafka 2.1.0.   Notable Issues Fixed in Cloudera Distribution of Apache Kafka 2.1.2:   KAFKA-3863: Add system test for connector failure/restart. KAFKA-3994: Deadlock between consumer heartbeat expiration and offset commit. All backported fixes can be viewed in the git release notes here or on our website under the Issues fixed section.   We look forward to you trying Kafka 2.1.2. For more information, please use the links below: Install or upgrade Kafka Review the documentation Review the Release Notes   As always, we welcome your feedback. Please send your comments and suggestions through our community forums. ... View more

Cloudera is happy to announce the availability of parcels and packages for Apache Kudu 1.4.0 / CDH 5.12.1. Apache Kudu 1.4.0 / CDH 5.12.1 is a bug fix release, with no new features or backwards incompatible changes.   To upgrade Kudu to 1.4.0 / CDH 5.12.1, see Upgrade Parcels or Upgrade Packages.   Issues Fixed in Kudu 1.4.0 / CDH 5.12.1:   KUDU-2085 - Fixed a bug that caused crashes when seeking past the end of prefix-encoded blocks. KUDU-2087 - Fixed an issue where Kudu would fail to start when Kerberos was enabled in FreeIPA-configured deployments. KUDU-2053 - Fixed a race condition in the Java RequestTracker. KUDU-2049 - Fixed an issue where scans on RLE-encoded integer columns would sometimes cause CHECK failures due to the CHECK condition being too strict. KUDU-2052 - Kudu now uses XFS_IOC_UNRESVSP64 ioctl to punch holes on xfs filesystems. This fixes an issue with slow startup times on xfs when hole punching was done via fallocate(). KUDU-1956 - Kudu will no longer crash if faced with a race condition when selecting rowsets for compaction. For a complete list of changes, bug fixes, and known issues, see the Kudu 1.4.0 / CDH 5.12.1 Release Notes.   As always, your feedback is appreciated. For general Kudu questions, visit the community page. If you have any questions related to the Kudu packages provided by Cloudera, including installation or configuration using Cloudera Manager, visit the Cloudera Community Forum. ... View more

Dear CDH, Cloudera Manager, and Cloudera Navigator users,   We are pleased to announce the release of Cloudera Enterprise 5.12.1 (CDH 5.12.1, Cloudera Manager 5.12.1, and Cloudera Navigator 2.11.1).   This release fixes key bugs and includes the following:   CDH fixes for the following issues: IMPALA-5615 - Compute Incremental stats is broken for general partition expressions IMPALA-5539 - Reading timestamps from Kudu are wrong with -use_local_tz_for_unix_ts IMPALA-5582 - Sentry privileges assigned to objects defined in uppercase can get deleted from the catalog IMPALA-5500 - Reduce catalog topic size when --compact_catalog_topic is enabled IMPALA-5579 - GetSchemas throws IndexArrayOutOfBoundsException if a table can't be loaded IMPALA-5616 - Add a new flag --enable_minidumps IMPALA-5524 - NullPointerException during planning with DISABLE_UNSAFE_SPILLS=TRUE HIVE-16845 - INSERT OVERWRITE a table with dynamic partitions on S3 fails with NPE HIVE-13588 - NPE is thrown from MapredLocalTask.executeInChildVM HIVE-12274 - Increase width of columns used for general configuration in the metastore. HIVE-16291 - Hive fails when unions a parquet table with itself HIVE-16930 - HoS should verify the value of Kerberos principal and keytab file before adding them to spark-submit command parameters HIVE-17050 - Multiline queries that have comment in middle fail when executed via "beeline -e" For a full list of upstream JIRAs fixed in CDH 5.12.1, see the issues fixed section of the Release Notes.   Cloudera Manager fixes for the following issues: Proper termination and cleanup of YARN applications during decommissioning: Fixed an issue where YARN applications may not exit gracefully or clean-up properly if hosts are decommissioned while application containers are still running. This could lead to unexpected container/application failure and/or orphaned container processes on YARN worker nodes. Now, when decommissioning a NodeManager or host running a NodeManager, Cloudera Manager first waits for the configured YARN graceful decommission timeout (if applicable), and allows additional time for ResourceManager to properly terminate the NodeManager and its child processes. Spilled memory not populated in Impala queries and in the Spilled Memory tab in the Cluster Utilization report: Fixed an issue where the Memory Spilled metric for each Impala query was not correctly populated. This prevented various features that depend on this metric from functioning correctly. For example, the Spilled Memory tab of the Cluster Utilization Report was not populated with data. This is now fixed. Threads CPU time and Total Time are not populated in Impala Query Monitoring: The Thread CPU Time and Total Time attributes of Impala Query Monitoring are now correctly populated. Hue Load Balancer caused login failure: Fixed an issue where using Apache httpd 2.4 as the Hue load balancer caused Hue logins to fail when TLS is enabled for Hue. This change requires Cloudera Manager to set the use_x_forwarded_host parameter in the hue.ini file to "true". After upgrading Cloudera Manager, Cloudera Manager will report that the Hue Server and Load Balancer role configurations are stale. If your cluster is affected by this bug, you must restart the Hue service. Exception thrown when searching log file: Fixes an issue where an exception might be thrown when searching a log when the log file size is larger than 2 GB. For a full list of issues fixed in Cloudera Manager 5.12.1, see the issues fixed section of the Release Notes.   For a full list of issues fixed in Cloudera Navigator 2.11.1, see the issues fixed section of the Release Notes.   We look forward to you trying the new release, using the information below: Download Cloudera Enterprise View the documentation   As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org. ... View more

Cloudera is happy to announce the availability of parcels and packages for Apache Kudu 1.3.0 / CDH 5.11.2. Apache Kudu 1.3.0 / CDH 5.11.2 is a bug fix release, with no new features or backwards incompatible changes.   To upgrade Kudu to 1.3.0 / CDH 5.11.2, see Upgrade Parcels or Upgrade Packages.   Issues Fixed in Kudu 1.3.0 / CDH 5.11.2: KUDU-2053 - Fixed a race condition in the Java RequestTracker. KUDU-2049 - Fixed an issue where scans on RLE-encoded integer columns would sometimes cause CHECK failures due to the CHECK condition being too strict. KUDU-1963 - Fixed an issue where the Java client misdiagnoses an error and logs a NullPointerException when a connection is closed by the client while a negotiation is in progress. KUDU-1853 - Fixed an issue where data blocks could be orphaned after a failed tablet copy. For a complete list of changes, bug fixes, and known issues, see the Kudu 1.3.0 / CDH 5.11.2 Release Notes.   As always, your feedback is appreciated. For general Kudu questions, visit the community page. If you have any questions related to the Kudu packages provided by Cloudera, including installation or configuration using Cloudera Manager, visit the Cloudera Community Forum. ... View more

Dear CDH, Cloudera Manager, and Cloudera Navigator users,   We are pleased to announce the release of Cloudera Enterprise 5.11.2 (CDH 5.11.2, Cloudera Manager 5.11.2, and Cloudera Navigator 2.10.2).   This release fixes key bugs and includes the following:   CDH fixes for the following issues: HIVE-11418 - Dropping a database in an encryption zone with CASCADE and trash enabled fails HIVE-11878 - ClassNotFoundException can possibly occur if multiple jars are registered one at a time in Hive HIVE-12762 - Common join on parquet tables returns incorrect result when hive.optimize.index.filter set to true HIVE-16660 - Not able to add partition for views in hive when sentry is enabled HIVE-16869 - Hive returns wrong result when predicates on non-existing columns are pushed down to Parquet reader IMPALA-5355 - Sentry Privileges and roles updated in the wrong order on impala restart IMPALA-5197 - Parquet scan may incorrectly report "Corrupt Parquet file" in the logs IMPALA-4293 - Query profile should include error log IMPALA-5355 - Sentry Privileges and roles updated in the wrong order on impala restart IMPALA-5208 - Forked breakpad process blocks indefinitely for WaitForContinueSignal and fails new Impalad process at startup IMPALA-5318 - Impala does not always generated fully qualified table names in audit events IMPALA-5615 - Compute Incremental stats is broken for general partition expressions For a full list of upstream JIRAs fixed in CDH 5.11.2, see the issues fixed section of the Release Notes.   Cloudera Manager fixes for the following issues: Make Oozie Load-balancer URL mandatory when enabling Oozie HA: Fixed an issue when the Oozie Load Balancer field in the Oozie configuration is not set and Oozie high availability is in use (two or more Oozie Server roles are deployed). This now creates a validation error and Cloudera Manager does not let you start or restart Oozie until the problem is fixed. Peak Memory Usage report for Impala is broken on CDH 5.11: Fixed an issue where the Impala Peak Memory Usage page in the Cluster Utilization Report did not display any data in Cloudera Manager versions 5.9 to 5.11. Agent process directories re-mounted on agent restart: Fixed an issue where restarting an agent on newer Linux distributions such as Ubuntu 16.04 or Red Hat 7 would result in process run directories being remounted and lost. Hostname parameter is not passed to Impala catalog role: IMPALA-5253 contained a security fix for clusters using Impala with TLS (SSL) security enabled. This fix was also made in several maintenance versions of CDH that require you to upgrade Cloudera Manager. If you upgrade to a CDH version with this fix without upgrading Cloudera Manager, Impala will not function when TLS is enabled for Impala. You should upgrade Cloudera Manager first if you want to move to a CDH version with the security fix. CDH versions with the Impala security fix: 5.11.1 5.10.2 5.9.3 5.8.5 To workaround this issue, upgrade to one of the following versions of Cloudera Manager before upgrading CDH: 5.12.0 5.11.2 5.10.2 5.9.3 5.8.6 For a full list of issues fixed in Cloudera Manager 5.11.2, see the issues fixed section of the Release Notes.   For a full list of issues fixed in Cloudera Navigator 2.10.2, see the issues fixed section of the Release Notes.   We look forward to you trying the new release, using the information below: Download Cloudera Enterprise View the documentation   As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org.   ... View more

Dear CDH, Cloudera Manager, and Cloudera Navigator users,   We are pleased to announce the release of Cloudera Enterprise 5.9.3 (CDH 5.9.3, Cloudera Manager 5.9.3, and Cloudera Navigator 2.8.3).   This release fixes key bugs and includes the following:   CDH fixes for the following issues: HIVE-11418 - Dropping a database in an encryption zone with CASCADE and trash enabled fails HIVE-14380 - Queries on tables with remote HDFS paths fail in "encryption" checks. HIVE-14564 - Column Pruning generates out of order columns in SelectOperator which cause ArrayIndexOutOfBoundsException HIVE-16660 - Not able to add partition for views in hive when sentry is enabled IMPALA-5355 - Sentry Privileges and roles updated in the wrong order on impala restart IMPALA-5193 - Impala reads gzip compressed text as binary when skip.header.line.count > 0 IMPALA-5197 - Parquet scan may incorrectly report "Corrupt Parquet file" in the logs IMPALA-4293 - Query profile should include error log For a full list of upstream JIRAs fixed in CDH 5.9.3, see the issues fixed section of the Release Notes.   Cloudera Manager fixes for the following issues: Low watermark value for Memstore Flush default is incorrect: For CDH versions 5.8 and higher, the Low Watermark for Memstore Flush configuration parameter is associated with the HBase parameter hbase.regionserver.global.memstore.lowerLimit. This value represents the fullness threshold of the memstore as a percentage of memstore capacity. The default value for this parameter was incorrectly set too low at .38. This can cause severe under utilization of the memstore. The default has been corrected to be .95. When upgrading to a version of Cloudera Manager with this fix, if the value was previously set to the old default of .38, it will automatically be increased to the new default, which may cause Cloudera Manager to mark your HBase service as having a stale configuration, requiring a restart. Additionally, if an existing Low Watermark for Memstore Flush configuration parameter has a value <= .9, it will be flagged as a configuration warning. Make Oozie Load-balancer URL mandatory when enabling Oozie HA: Fixed an issue when the Oozie Load Balancer field in the Oozie configuration is not set and Oozie high availability is in use (two or more Oozie Server roles are reployed). This now creates a validation error and Cloudera Manager does not let you start or restart Oozie until the problem is fixed. For a full list of issues fixed in Cloudera Manager 5.9.3, see the issues fixed section of the Release Notes.   For a full list of issues fixed in Cloudera Navigator 2.8.3, see the issues fixed section of the Release Notes.     We look forward to you trying it, using the information below: Download Cloudera Enterprise View the documentation   As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org.   ... View more

Cloudera is happy to announce the availability of parcels and packages for Apache Kudu 1.2.0- CDH 5.10.2. Apache Kudu 1.2.0- CDH 5.10.2 is a bug fix release, with no new features or backwards incompatible changes.   To upgrade Kudu to 1.2.0- CDH 5.10.2, see Upgrade Parcels or Upgrade Packages.   Issues Fixed in Kudu 1.2.0- CDH 5.10.2: KUDU-1933 - Fixed an issue that truncated the 64-bit log index in the OpId to 32 bits, causing overflow of the log index. KUDU-1607 - Fixed an issue where Kudu could not delete failed tablets using the DROP TABLE command. KUDU-1905 - Allow reinserts on tables when all columns are part of the primary key. KUDU-1893 - Made a fix to avoid incorrect NULL results and ensure evaluation of predicates for columns added after table creation. For a complete list of changes, bug fixes, and known issues, see the Kudu 1.2.0/ CDH 5.10.2 Release Notes.   As always, your feedback is appreciated. For general Kudu questions, visit the community page. If you have any questions related to the Kudu packages provided by Cloudera, including installation or configuration using Cloudera Manager, visit the Cloudera Community Forum. ... View more

Dear CDH, Cloudera Manager, and Cloudera Navigator users,   We are pleased to announce the release of Cloudera Enterprise 5.10.2 (CDH 5.10.2, Cloudera Manager 5.10.2, and Cloudera Navigator 2.9.2).   This release fixes key bugs and includes the following:   CDH fixes for the following issues: HADOOP-12751 - While using kerberos Hadoop incorrectly assumes names with '@' to be non-simple HBASE-16630 - Fragmentation in long running Bucket Cache HIVE-12768 - Thread safety: binary sortable serde decimal deserialization HIVE-14564 - Column Pruning generates out of order columns in SelectOperator which cause ArrayIndexOutOfBoundsException IMPALA-4725 - Query option to control Parquet array resolution IMPALA-4546 - Fix Moscow timezone conversion after 2014 IMPALA-4822 - Implement dynamic log level changes IMPALA-5487 - Race in runtime-profile.cc::toThrift() can lead to corrupt profiles being generated while query is running For a full list of upstream JIRAs fixed in CDH 5.10.2, see the issues fixed section of the Release Notes.   Cloudera Manager fixes for the following issues: The cloudera-server-db fast_stop fails on Debian-based systems: Fixed an issue where the cloudera-server-db fast_stop command fails on non-sytemd Debian systems like Debian 7 with a command not found error HBase configuration is supplied for Hive when HBase service is not selected: Fixed an issue where Cloudera Manager provided configuration for the hive-site.xml file even if the HBase Service setting in Hive is not selected, which could cause unnecessary errors when Hive-on-Spark attempts to connect to HBase. Cloudera Manager now correctly emits the HBase-related configuration in the hive-site.xml only when Hive is dependent on HBase For a full list of issues fixed in Cloudera Manager 5.10.2, see the issues fixed section of the Release Notes.   Cloudera Navigator fixes the following issues: Bulk extraction triggered can result in orphaned relations: In some cases, HDFS bulk extraction was being triggered due to an error in incremental extraction. Specifically, Cloudera Navigator was resetting the long identity of HDFS elements resulting in orphaned relations. For a full list of issues fixed in Cloudera Navigator 2.9.2, see the issues fixed section of the Release Notes.   We look forward to you trying it, using the information below: Download Cloudera Enterprise View the documentation   As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org. ... View more

Dear CDH, Cloudera Manager, and Cloudera Navigator users,   We are pleased to announce the release of Cloudera Enterprise 5.11.1 (CDH 5.11.1, Cloudera Manager 5.11.1, and Cloudera Navigator 2.10.1).   This release fixes key bugs and includes the following:   CDH fixes for the following issues: HADOOP-14028 - S3A BlockOutputStreams doesn't delete temporary files in multipart uploads or handle part upload failures HIVE-12768 - Thread safety: binary sortable serde decimal deserialization IMPALA-5251 - DecimalAvgFinalize() gets the wrong arg type IMPALA-5186 - Handle failed CreateAndOpenScanner() in MT scan. IMPALA-3641 - DROP / CREATE sequence on same table failed with "table already exists". IMPALA-4902 - Concurrent DDL may fail with a ConcurrentModificationException. IMPALA-5253 - Use appropriate transport for StatestoreSubscriber IMPALA-5145 - CTAS failing when creating from a view with error "Unsupported type 'null_type'" For a full list of upstream JIRAs fixed in CDH 5.11.1, see the issues fixed section of the Release Notes.   Cloudera Manager fixes for the following issues: Automated Cloudera Manager installer fails on Ubuntu 16.04: Fixed an issue where running the cloudera-manager-installer.bin installer file (as described in the documentation) fails on Ubuntu 16.04 LTS (Xenial). Accessing Sqoop2 with Hue fails: Fixed an issue where accessing Sqoop2 with Hue fails with the following error: Sqoop error: Could not get connectors.  Drop-down options not visible when using Internet Explorer 11: Fixed an issue that prevents Internet Explorer from rendering the add/edit resource pool dialog box. All required fonts are now installed by Cloudera Manager: Fixed an issue where Cloudera Manager made requests to googleapi.com to download some of its required fonts, which fails if the browser does not have Internet access. Cloudera Manager now includes all of the necessary fonts. For a full list of issues fixed in Cloudera Manager 5.11.1, see the issues fixed section of the Release Notes.   Cloudera Navigator fixes the following issues: Bulk extraction triggered can result in orphaned relations: In some cases, HDFS bulk extraction was being triggered due to an error in incremental extraction. Specifically, Cloudera Navigator was resetting the long identity of HDFS elements resulting in orphaned relations. For a full list of issues fixed in Cloudera Navigator 2.10.1, see the issues fixed section of the Release Notes.     We look forward to you trying it, using the information below: Download Cloudera Enterprise View the documentation   As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org. ... View more