IBM Support

How to configure gremlinPool in Db2 Graph to prevent pod restart when excuting long-running queries

How To


Summary

On CP4D, the default value of gremlinPool is not sufficient for long-running queries and the health-check code that automatically runs against the pod.

When the long running loop query is running, THE value for gremlinPool is not sufficient to continue your query and respond to the health checks. When the health checks are not responded to in a timely manner this causes the deployment to believe they are unhealthy and thus terminates the pod and restarts it. This causes the restart of the pod.

To prevent this issue, you are recommended to set gremlinPool to 8.

In the CP4D 4.5.0 release, the default value for gremlinPool is increased, so this issue is resolved.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PkpAAE","label":"OTHER - Uncategorized"}],"ARM Case Number":"TS009829699","Platform":[{"code":"PF016","label":"Linux"}],"Version":"11.5.7"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
30 April 2025

UID

ibm16606259

Page Feedback