This topic describes the supported configurations and system requirements for GemFire XD.
This release of GemFire XD is not provided as a standalone product. It is instead delivered as part of Pivotal HD Enterprise, and it requires Pivotal HD to be installed on the same machine in order to provide HDFS and HAWQ integration features. HDFS support is limited to Pivotal HD Hadoop.
Use the Pivotal Command Center CLI (Command Line Interface) to install GemFire XD. The Pivotal Command Center CLI installation process installs multiple instances of GemFire XD on different servers, along with HDFS, MapReduce, and other components you choose to install. See the Pivotal HD Enterprise Installation and Administrator Guide for more information.
The following table shows all supported configurations for GemFire XD.
|Operating System||Processor Architecture||JVM|
|Red Hat EL 6.2, 6.4||x86 (64bit)||
Java SE 1.7.0_05
Java SE 1.6.0_26*
|CentOS 6.2, 6.4||x86 (64bit)||
Java SE 1.7.0_05
Java SE 1.6.0_26*
*Pivotal HD version 2.0.1 does not support Java 1.6. If you intend to use GemFire XD with Pivotal HD version 2.0.1 or later, use Java SE 1.7.0_05.
Many default Linux installations use SYN cookies to protect the system against malicious attacks that flood TCP SYN packets. The use of SYN cookies dramatically reduces network bandwidth, and can be triggered by a running GemFire XD distributed system.
If your GemFire XD distributed system is otherwise protected against such attacks, disable SYN cookies to ensure that GemFire XD network throughput is not affected.
net.ipv4.tcp_syncookies = 0
Setting this value to zero disables SYN cookies.
GemFire XD supports two JDBC drivers: a thin client JDBC driver and a peer JDBC driver. GemFire XD server instances and the peer driver are supported only with Java SE 6. You can download Java from http://www.oracle.com/technetwork/java/javase/downloads/index.htm.
In addition, GemFire XD now supports an ODBC driver that responds to ODBC API function calls in client applications. The GemFire XD ODBC driver supports ODBC 3.5 APIs and the unixODBC and iODBC driver managers. The driver is a separate installation download from GemFire XD. SeeUsing ODBC Driver Functions in Client Applications for more information on driver installation requirements.
Severe performance degradation can occur for insert-heavy workloads when GemFire XD and Hadoop run on the same machine and GemFire XD is configured with very large memory sizes (either off-heap or on-heap memory). The performance degradation occurs when the operating system pages out GemFire XD memory to disk.
To permanently change the default limit for all users, edit the /etc/security/limits.conf file and add the line:
* hard memlock limit-value-in-kb
Note: If you do not increase the "ulimit -l" value to at least the amount of memory used by GemFire XD, then GemFire XD will fail to start when you specify -lock-memory.
$ echo 1 > /proc/sys/vm/drop_caches
|Client Timeout Property||Recommended Value|
Using these values ensures that GemFire XD read operations to Hadoop quickly fail if the Hadoop node is unavailable (instead of hanging for a long period of time due to the default timeout intervals).
Due to the memory requirements and memory configuration required for each product, Pivotal does not support production deployments of GemFire XD and HAWQ on the same machine. Deploy GemFire XD and HAWQ on the same machine or virtual machine only for development or testing purposes.