GPSS session persists long time with IDLE session
Article ID: 296797
Updated On:
Products
VMware Tanzu Greenplum
Issue/Introduction
Sometimes, we will see some GPSS sessions lasting with IDLE status for long. In such case, admins have to manually kill them to release connection slots. And we will always find the last query these sessions were running is "select version()".
Environment
Product Version: 6.20
Resolution
Here below is the cause of the issue:
GPSS clients will send "select version()" to test the connectivity with the server. When the running time hits the TIMEOUT, the session will be identified as a failed one, and it will be in IDLE status for long. In most cases, the long running "select version()" should be due to high load, which is another topic.
The TIMEOUT mentioned previously is controlled by a GUC named "GPDB_CONNECT_TIMEOUT"
The fix is to be released with GPSS 1.9.1. The fix is to release IDLE GPSS sessions in time when the TIMEOUT is hit.
GPSS clients will send "select version()" to test the connectivity with the server. When the running time hits the TIMEOUT, the session will be identified as a failed one, and it will be in IDLE status for long. In most cases, the long running "select version()" should be due to high load, which is another topic.
The TIMEOUT mentioned previously is controlled by a GUC named "GPDB_CONNECT_TIMEOUT"
The fix is to be released with GPSS 1.9.1. The fix is to release IDLE GPSS sessions in time when the TIMEOUT is hit.
Feedback
Yes
No
Powered by
