Release Notes

WD Fusion 2.5.5 Build 527 - 26 August 2015

This release includes updated support for Pivotal HD.

Available Packages

WD Fusion currently supports the following versions of Hadoop:

• CDH 5.2.0
• CDH 5.3.0
• CDH 5.4.0
• HDP 2.1.0
• HDP 2.2.0
• MAPR 4.0.1 ^*
• MAPR 4.0.2 ^*
• MAPR 4.1.0 ^*
• Pivotal HD 3.0.0 ^*

System Requirements

Before you install this software you must ensure that you meet the necessary system, software and hardware requirements for running WD Fusion. See a full checklist in our online user guide: docs.wandisco.com/bigdata/wdfusion/

Supported Hadoop Packages:

Certified Platforms / DBMS & DConE Support:

• HDP2.1.2 - 2.2.X
• PHD3.0
• CDH5.15 5.4
• EMC Isilon 7.2
• MapR M5,7
• DConE 1.3
• MySQL (Hive MetaStore)

Client Applications Supported:

• Hive
• SparkSQL
• Impala* Some current limitations - contact WANdisco's solutions team
• HBase
• SQOOP
• Flume
• Kafka
• Storm

Installation

You can find detailed instructions on how to get up and running in our online user guide:
- docs.wandisco.com/bigdata/wdfusion/install.html#procedure

Upgrades from an earlier version:

It's essential that you remove previously installed versions of WD Fusion before you complete a new installation:
- docs.wandisco.com/bigdata/wdfusion/install.html#cleanup

Previous Release Notes:

You can view the release notes for previous releases in the release archive:
- docs.wandisco.com/bigdata/wdfusion/archive.html

New Features

• Added WD Fusion UI support for Pivotal HD 3.0.0 FUI-709

Known Issues

• MapReduce applications currently don't work with fusion:/// because the WD Fusion client jars were not picked up on the classpath. This will be fixed in the next release, for now a workaround is to add /opt/wandisco/fusion/client/lib/* to mapreduce.application.classpath in mapred-site.


• Incorrect configuration of the proxy user, when Setting up Kerberos can result in permission errors in the log that contain the following text:

   "<hostname> is not allowed to impersonate <systemyser>"

  The proxy user setup must refer to the system user that runs WD Fusion, for example, if system user "hdfs" is running WD Fusion, then the proxyuser settings would be:

  <property>
  <name>hadoop.proxyuser.hdfs.users</name>
  <value>*
  </property>
   
  <property>
  <name>hadoop.proxyuser.hdfs.groups</name>
  <value>*</value>
  </property>

  FUI-1012

WD Fusion 2.5.4 Build 520 - 24 August 2015

New Features

• Replicated folders Details pages now display their total data size on the title bar of the folder. FUI-524

Fixes

• Fixed issue with persisting the core-site.xml properties in HDP2.1/Ambari1.6 clusters. FUI-647


• Installing WD Fusion onto a Kerberized environment has been improved. Kerberos configuration can now be handled by the installer, with some additional steps - Setting up Kerberos. FUI-658

WD Fusion 2.5.2 Build 457 - 3 August 2015

Fixes

• Fixed an issue where running the consistency check tool on a newly created empty replicated folder would fail. FUI-846


• Fixed issue with WD Fusion UI log placement. Now all WD Fusion logs are located in /var/log/fusion/... FUI-754


• Fixed issue with missing installer breadcrumbs. FUI-803


• Fixed an issue where validation of the license file caused errors to be logged due to bad license data transfer limits. FUI-745


• Installing WD Fusion on a Kerberized cluster has been simplified. Configuration can now be set from within WD Fusion's installer. FUI-493


• When Kerberos is enabled through the installer, the kerberos.generated.config.path is now set to a location that is writable for the installer. The UI controller for Kerberos values are now regenerated in the Kerberos conf file when the values are changed. FUI-742


• Default configuration has now changed so that WD Fusion and IHC servers will bind to all available IP addressed, resolving potential communication problems that may have occurred on multi-homed servers. FUI-750,FUI-815

Known Issues

• At present it is not possible to run WD Fusion on a HDP cluster that is managed by Ambari 1.6. FUI-783


• There's a known issue concerning Cloudera Manager's startup script when using parcels on a system that is running Hive. The variable HIVE_AUX_JARS_PATH does not accept a comma separated list of jar files, as is described in the documentation. FUI-751


• The requirements for installation onto Kerberized clusters has been clarified in the online User Guide. See Kerberos Security.

WD Fusion 2.5.1 Build 366 - 14 July 2015

New features

• Adds WD Fusion Impala Parcel to support impala reads from a non-HDFS URI. FUI-577

Fixes

• Added documentation on how to install clients using Cloudera's parcels or Hortonworks stacks. FUI-660

Known Issues

• Known issue with Location names. You must use different Location names /Node IDs for each zone. If you use the same name for multiple zones then you will not be able to complete the induction between those nodes. FUI-594


• Spark files input can't be used for streaming from replicated folders directly and checkpointing could work incorrectly. FUS-611


• Hive from CDH 5.3 does not work with WD Fusion, as a result of HIVE-9991. The issue will be addressed once this fix for Hive is released.


• Do not locate WD Fusion on the same server as other HDFS processors, especially DataNodes. HDFS's default block placement policy dictates that if a client is co-located on a DataNode, then that co-located DataNode will receive 1 block of whatever file is being put into HDFS from that client. This means that if the WD Fusion Server (where all transfers go through) is co-located on a DataNode, then all incoming transfers will place 1 block onto that DataNode. In which case the DataNode is likely to consumes lots of disk space in a transfer-heavy cluster, potentially forcing the WD Fusion Server to shut down in order to keep the Prevaylers from getting corrupted. FUS-453


• Impala does not work with WD Fusion. Impala is not able to read data from non-HDFS file systems, which is how Impala sees Fusion. With Fusion 2.3 a Fusion Impala client (See Impala Parcel) will be available that will enable Fusion to support Impala reads without modifications to CDH, the Hive Metastore, or the customer's Impala applications. This should satisfy the vast majority of customer use cases, since Impala is typically used for fast read performance. Most customers use Hive to write data to HDFS and modify the Hive metastore, which Impala also uses.
  
  If the customer is using Impala for both reads and writes a workaround is available to the field upon request. FUS-476

WD Fusion 2.5.1 Build 323 - 2 July 2015

Known Issues

• Very large numbers of inconsistent objects that are reported after a consistency check currently causes a significant UI performance hit. In the next release, consistency check results will be paginated to improve performance. FUI-57

New features

Fixes