2.06 - Prerequisites - Teradata QueryGrid

The following minimum requirements must exist before installing Teradata QueryGrid and one or more of the following licensed connectors:

Teradata connector for Teradata Database
Hive connector for CDH and HDP
Presto connector for Presto, CDH, or HDP
Spark SQL connector for CDH and HDP
Oracle connector for Oracle Database

For more information, log in to https://access.teradata.com and search for KCS001621.

Requirements

Component	Requirements
System (Data Source)	Refer to the compatibility matrix for database and SLES version compatibility. For more information, log in to https://access.teradata.com and search for KCS001621. The following systems on SLES 10 or 11, or Red Hat 6 or 7: CDH 5.11 and later (the Hive connector requires Java 8 or later on the cluster) HDP 2.4 and later (the Hive connector requires Java 8 or later on the cluster) Presto 167t and later (Presto Admin must exist on the cluster) For the Hive connector, the Java 8 or later Teradata/Oracle JDK is preferred. For the Hive connector, Hive Client must be installed on all driver nodes in the system. For the Oracle target connector requirements, see Completing the Oracle Connector Configuration.
Teradata Viewpoint	Viewpoint 16.10, 16.20 and later. The QueryGrid portlet package must be installed on the Viewpoint server. The Viewpoint 16.10 edition must support multiple-system monitoring. QueryGrid 2.0x cannot be configured on Viewpoint editions that support only single-system monitoring.
Kerberos	For environments secured with Kerberos, the most current version of Kerberos available.
Java	The latest version of Java 8 on the driver node or nodes in an initiating system (data source). A driver node invokes the connector method (for example, Teradata Database) used for a query on a target system (data source). The Teradata/Oracle JDK is preferred.
TMS, Server, or VM for QueryGrid Manager	One or more (separate server for each QueryGrid Manager instance). Important: Do not install QueryGrid Manager on existing TMS servers hosting Viewpoint, Data Mover, Ecosystem Manager, and so forth, unless those products are uninstalled and the server is re-purposed to be a QueryGrid Manager server. Hardware requirements (minimum): 2 CPUs 16 GB RAM 250 GB hard disk space available at /var/opt/teradata/tdqgm Operating system: SLES 11 or 12 Red Hat 6 or 7 The latest version of Java 8 on any TMS, server, or VM on which Teradata QueryGrid Manager is being installed. The Teradata/Oracle JDK is preferred. See QueryGrid Manager planning section below.
Network	Network connectivity between the Teradata nodes and Hadoop master node, and all Hadoop data nodes, through customer LAN, BYNET, or InfiniBand.

Number of QueryGrid Manager Instances

For each Data Center, determine the number of QueryGrid Managers needed. One instance of QueryGrid Manager is installed on one TMS or customer-supplied server, or VM.

Use the following guidelines. The guidelines are based on the minimum hardware requirements for the TMS, server, or VM.

Per Data Center	Description
Minimum number of QueryGrid Manager instances	One instance for approximately every 200 Teradata QueryGrid-connected nodes This approximation is based on moderate query volume on minimum supported hardware requirements. Actual required number varies depending on server specs and query volume. New QueryGrid managers can be added if load is high on existing instances to reduce overall load.
Minimum number of QueryGrid Manager instances for high availability (HA)	Two instances More than two instances can be deployed. Multiple instances can be clustered for high availability and scalability. Each instance in a cluster is fully active and maintains a full copy of the QueryGrid configuration.
Number of QueryGrid Manager instances to keep communication, heartbeats, query metrics, and log data local to a Data Center	At least one per Data Center, more if the number of nodes in the Data Center exceed the resource requirements of the single QueryGrid Manager instance

Port Availability

Ensure that network ports are open between QueryGrid-attached systems (data sources) and QueryGrid Manager. Systems include the Teradata Database nodes, Hadoop master node, all Hadoop data nodes, and Presto nodes.

The following illustration shows the port numbers used between QueryGrid-attached systems and QueryGrid Manager in a fabric.

Port	Description
22	One-way connection from Teradata QueryGrid Manager to all QueryGrid-attached nodes; used if performing automatic installation of packages. One-way connection from Teradata QueryGrid Manager to another Teradata QueryGrid Manager; used during cluster creation when using the SSH method.
1025	One-way connection from the target Teradata connector (driver) to the target Teradata Database systems (JDBC connection).
5000-5001	Two-way connections between all QueryGrid-attached nodes; other available ports can be used, but ports 5000-5001 are recommended.
7000-7001	Two-way connections between clustered Teradata QueryGrid Managers.
8080	One-way connection from the target Presto connector (driver) to the target Presto coordinator.
8443	One-way connection from the target Hive connector (driver) to the Apache Knox Gateway if Apache Knox Gateway is enabled on Hadoop nodes.
9300-9303	Two-way connections between clustered Teradata QueryGrid Managers.
9443	One-way HTTPS connection from Viewpoint or a browser to Teradata QueryGrid Manager. One-way connection from Teradata QueryGrid Manager to another Teradata QueryGrid Manager; used during cluster creation when using the join token method.
9444	One-way HTTPS connection from QueryGrid-attached nodes to Teradata QueryGrid Manager.
9445	Two-way HTTPS connection between clustered Teradata QueryGrid Managers in a fabric.
10000	One-way connection between the target Hive connector (driver) to target Hiveserver 2.
10016	One-way connection from the target Spark SQL connector (driver) to the target Spark Thrift Server.