VMware

VMware vSphere Big Data Extensions 2.0 Release Notes

vSphere Big Data Extensions 2.0 | 3 October 2014 | Build 1885370

Check these release notes for additions and updates.

What's in the Release Notes

These release notes apply to vSphere Big Data Extensions 2.0 and cover the following topics:

What's New in vSphere Big Data Extensions 2.0

Big Data Extensions enables the rapid deployment of a Hadoop cluster on a VMware vSphere virtual platform. This release provides the following new features and enhancements.

  • Support for the Latest Distributions of Apache Hadoop Software. In additon to the previously supported Hadoop distributions, Big Data Extensions users may now also deploy Apache Bigtop 0.7.0, Cloudera CDH5, Hortonworks HDP 2.1, MapR 3.1, and Pivotal PHD 2.0.

  • CentOS 6.4 Operating System for the Hadoop Template Virtual Machine. The Hadoop Template Virtual Machine now uses CentOS 6.4 as its default operating system. This provides an increase in performance, as well as support for all Hadoop distributions for use with Big Data Extensions.

  • IPv6 Support for Serengeti Management Server Network. You can use IP version 6 (IPv6) for network addressing within the Serengeti Management Server network.

  • Support for Internationalization (I18N) Level 1. You can specify vCenter Server resources using any character set supported by the vCenter Server system on which you deploy Big Data Extensions. For example, you can specify resources such as datastores labeled using non-English characters.

  • Serengeti Management Server Administration Portal. You can verify that Big Data Extensions has successfully started, and that the Serengeti Services are running using the Serengeti Management Server Administration Portal. The Serengeti Management Server Administration Portal also lets you view error messages related to specific services so that you can troubleshoot issues preventing your Big Data Extension deployment from successfully initializing, and recover services that may not have successfully started.

  • Improved Error Handling. To help you more easily identify, understand, and recover from error conditions, Big Data Extensions provides improved error handling and reporting

  • Big Data Extensions Upgrade. You can upgrade from Big Data Extensions 1.0 or 1.1 to the current version and preserve all the data within the clusters under Big Data Extensions management. All of your existing clusters will be available to be managed by Big Data Extensions once the upgrade to Big Data Extensions 2.0 is complete.


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 can not upgrade to the released version. Instead, you must create a new Big Data Extensions environment, and install the new version of the software.


Notes for the Product Guides

The following information is not currently addressed by the product guides.

  • Do not use Big Data Extensions is 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 used with Big Data Extensions, it will disrupt the placement policies of your Big Data cluster virtual machines.


Resolved Issues

The following issue has been resoloved for Big Data Extensions 2.0.

  • A critical security vulnerability in the Bash shell, referred to as Shellshock, has been identified.

    Exploitation of this issue might lead to remote code execution. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the following names to this issue:

    • CVE-2014-6271
    • CVE-2014-7169
    • CVE-2014-7186
    • CVE-2014-7187
    • CVE-2014-6277
    • CVE-2014-6278

    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 issue. To remediate this issue, you must install and apply the BDE 2.0 Patch 1. To learn more about Shellshock security issues, and how to download and install the patch, see VMware Knowledge Base article #2091050.

  • The Big Data Extensions plug-in fails to add datastores in environments which use VMware Virtual SAN or Network Attached Storage.

    The Big Data Extensions plug-in, a graphical user interface integrated with vSphere Web Client, would fail when you attempted to add a datastore of any type from a vSphere environment that included either a VMware Virtual SAN or Network Attached Storage (NAS) datastore. The failure would occur when the Big Data Extensions plug-in attempted to list the available datastores.

    This issue has been fixed, and you can now add datastores using the Big Data Extensions plug-in when using VMware Virtual SAN or Network Attached Storage.


Known Issues

Big Data Extensions 2.0 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.

  • 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 contains non-ASCII characters, 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 the installation.

  • 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 will fail 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.