VMware vSphere Big Data Extensions 2.1 Release Notes
vSphere Big Data Extensions 2.1 | 14 October 2014 | Build 2173865
Last Updated on 13 March 2016.
Check these release notes for additions and updates.
What's in the Release Notes
These release notes apply to vSphere Big Data Extensions 2.1 and cover the following topics:
What's New in vSphere Big Data Extensions 2.1
Big Data Extensions enables the rapid deployment of Hadoop clusters on a VMware vSphere virtual platform. This release provides
the following new features and enhancements.
Integration with Partner Hadoop Management Tools. Through the Big Data Extensions GUI or
CLI, you can seamlessly create virtual machines for a Hadoop cluster and use a Cloudera Manager or Apache
Ambari application manager to perform the software installation and cluster management.
HBase Only Clusters. You can create an HBase only cluster that points to an existing
Apache-based Hadoop HDFS
or EMC Isilon OneFS.
Compute Workers Only Cluster. You can create a compute workers only cluster that
contains only MapReduce compute workers nodes, for example TaskTracker or NodeManager, and add them into either an existing
physical or virtual Hadoop cluster.
Updated Support for the Latest Hadoop Distributions. In addition to the previously supported
Hadoop distributions, Big Data Extensions also supports Apache Bigtop 0.8.0, Cloudera CDH 5.1.3, Hortonworks HDP 1.3.8, and Pivotal PHD 2.0.1 and 2.1.
Big Data Extensions Upgrade. You can upgrade Big Data Extensions 2.0 to the current version,
Big Data Extensions 2.1, and preserve all the data for the clusters created in Big Data Extensions. All of your existing
clusters can be managed by Big Data Extensions once the upgrade completes.
Installation Notes for This Release
Read the vSphere Big Data Extensions documentation for step-by-step
instructions on installing and configuring Big Data Extensions.
If you installed the Beta edition of Big Data Extensions, you cannot upgrade to the released version.
Instead, you must create a new Big Data Extensions environment, and install the new version of the software.
Updated If you currently have Big Data Extensions version 1.x and want to upgrade to version 2.1, you must upgrade to version 2.0 first and then upgrade to version 2.1. You cannot upgrade directly from Big Data Extensions version 1.x to version 2.1.
When you use the Virtual Update Manager (VUM) to upgrade the Big Data Extensions 2.0 vApp to Big Data Extensions 2.1 vApp, VUM
reports that the upgrade completed successfully, but VUM only upgrades the Big Data Extensions Management Server, not the Big Data
Extensions hadoop template. For more information on this issue, see KB #2090078.
The following issues have been resolved for Big Data Extensions 2.1.
- Updated A critical security vulnerability exploiting the stack buffer overflow in the glibc library was disclosed.
If you are running Big Data Extensions 2.1, your environment is vulnerable to Common Vulnerability and Exposure (CVE) security issue CVE-2015-7547. You should install and apply the patch to address this issue.
For information on the patch, and instructions on how to download and install it, see KB #2144423.
- Updated A critical security vulnerability in the Java Runtime Environment, referred to as SKIP-TLS, has been identified.
To address this issue, Big Data Extensions now includes a security update that addresses Common Vulnerability and Exposure (CVE) items. The Oracle (Sun) Java Runtime Environment (JRE) package is updated to 1.7.0_80. The update addresses multiple security issues that exist in the earlier releases of Oracle (Sun) JRE. Oracle has documented the CVE identifiers that are addressed in JRE 1.7.0_80 in the Oracle Java SE Critical Patch Update Advisory. The JRE update fixes CVE-2015-0488, CVE-2015-0478, and CVE-2015-0204
If you are running Big Data Extensions 2.1, your environment is vulnerable to the CVE security issues noted above. You should install and apply the patch to address these security issues.
For more information on the patch and instructions on how to
download and install it, see KB #2116604.
- A critical security vulnerability in the Bash shell, referred to as Shellshock, has been
Big Data Extensions might use the Bash shell that is part of the Linux operating system.
If the operating system has a vulnerable version of Bash, the Bash security vulnerability might be
exploited through Big Data Extensions.
If you are running Big Data Extensions 2.0, your environment is vulnerable to the Bash
shell security bug. You should install and apply the BDE 2.0 Patch 1.
For more information on the patch and instructions on how to
download and install it, see KB #2091050.
Unable to delete a cluster after two clusters are deployed with overlapping IP ranges
If you deploy two clusters with overlapping IP ranges and then try to delete the two clusters, one of the clusters is not deleted cleanly.
The vCenter objects for the second cluster, including such things as virtual machines and resource pools, are deleted, however, the database
entries still exist.
- Serengeti is unable to communicate with vCenter server using the vCenter Extension Service
Serengeti is unable to communicate with vCenter server using the vCenter Extension Service because vCenter
lost the Big Data Extensions registration.
Big Data Extensions has a configuration item that records if it has been registered before. If Big Data Extensions has been registered before, it does not attempt to register again. When this happens, the login for Big Data Extensions is rejected.
Big Data Extensions 2.1 has the following known issues. If you encounter an issue that is not in this known
issues list, search the VMware
Knowledge Base, or let us know by contacting
VMware Technical Support.
Updated Upgrading from Big Data Extensions version 1.x directly to version 2.1 is not supported
When you try to upgrade Big Data Extensions version 1.x, you can see version 2.1 in the Virtual Update Manager (VUM) wizard but a direct upgrade from version 1.x to 2.1 is not supported. You must upgrade from Big Data Extensions version 1.x to version 2.0 first, and then upgrade to version 2.1.
Do not use Big Data Extensions in conjunction with vSphere Storage DRS
Big Data Extensions places virtual machines on hosts according to available resources, Hadoop best practices,
and user defined placement policies prior to creating virtual machines. For this reason, you should not
deploy Big Data Extensions on vSphere environments in combination with Storage DRS. Storage DRS continuously
balances storage space usage and storage I/O load to meet application service levels in specific environments.
If Storage DRS is used with Big Data Extensions, it will disrupt the placement policies of your Big Data cluster virtual
Installation of Big Data Extensions fails if the user name of the logged-in user contains non-ASCII characters
If the user name of the user who is currently logged in to Big Data Extensions contains non-ASCII characters, the installation of Big Data
Extensions fails with the error message: An internal error has occurred - Error #1009.
Workaround: Log in with a user name that does not contain non-ASCII characters and retry
Migrating virtual machines in vCenter Server may disrupt the virtual machine placement policy
Big Data Extensions places virtual machines based on available resources, Hadoop best practices, and user
defined placement policies that you specify. For this reason, DRS is disabled on all the virtual machines
created within the Big Data Extensions environment. While this prevents virtual machines from being automatically
migrated by vSphere, it does not prevent you from inadvertently moving virtual machines using the vCenter
Server user interface. This may break the Big Data Extensions defined placement policy. For example, this
may disrupt the number of instances per host and group associations.
Workaround: If you need to migrate Big Data Extensions virtual machines, carefully plan
the migration to ensure the placement policy is not disrupted during migration.
Temporarily powering off hosts will cause Big Data clusters to fail during cluster creation
When creating Big Data clusters, Big Data Extensions calculates virtual machine placement according to
available resources, Hadoop best practices, and user defined placement policies prior to creating the
virtual machines. When performing placement calculations, if some hosts are powered off or set to stand-by,
either manually, or automatically by VMware Distributed Power Management (VMware DPM), those hosts will not
be considered as available resources when Big Data Extensions calculates virtual machine placement for use
with a Big Data cluster.
If a host is powered off or set to stand-by after Big Data Extensions calculates virtual machine placement,
but before it creates the virtual machines, the cluster fails to create until you power on those hosts.
Workaround: The following workarounds can help you both prevent and recover from this issue.
Disable VMware DPM on those vSphere clusters where you deploy and run Big Data Extensions.
Put hosts in maintenance mode before you power them off.
If a Big Data cluster fails to create due to its assigned hosts being temporarily unavailable, resume the
cluster creation after you power-on the hosts.