Resolved Issues | Teradata QueryGrid 02.12.00.00 - 2.12 - Resolved Issues - Teradata QueryGrid

Teradata® QueryGrid™ Release Definition

Product
Teradata QueryGrid
Release Number
2.12
Release Date
July 2020
Content Type
Release Notes
Publication ID
B035-5992-030C
Language
English (United States)

Resolved issues are corrections to Teradata QueryGrid, including related documentation.

02.12.00.01

Issue Description
QUERYGRID-13948 DB/Node gets hung with High consumption of CPU by QGLMain process

02.12.00.00

Teradata QueryGrid 02.12.00.00 consists of the following resolved issues:
Issue Description
QUERYGRID-12469 QGM: "completed queries" portlet is showing "success" for failed "SQLs"
QUERYGRID-12519 Node: Existing rotated logs files are not pushed on tdqg-node restart
QUERYGRID-12540 Hive/Presto/Spark connector: Low buffer utilization due to the way we estimate string column size
QUERYGRID-12542 Swagger doc: filterByProxySupport should be under GET /config/systems instead of GET /config/bridges
QUERYGRID-12599 QGL: queries are failing with SHM alloc failure due to incorrect overall SHM memory validation
QUERYGRID-12824 QGM: import doesn’t work when a node is using a non-default network interface as the proxy network
QUERYGRID-12827 Driver: failure to write very large error messages
QUERYGRID-12833 Fabric: Driver fails with UnsatisfiedLinkError
QUERYGRID-13134 QGI: KeyedObjectPool can destroy connection used by another request
QUERYGRID-13434 QGM: Nodes falsely reported offline due to ElasticSearch "No subject alternative DNS name matching" error
QUERYGRID-13447 Fabric: Initiator nodes with high CPU during link bandwidth test was observed