Replies: 1 comment 5 replies
-
Hi @anup-krai 👋 120 seems enough already but you can try increasing it. What I would focus on is the resource consumption of Kong GW deployment. Have you checked if it's not running near its limits (CPU and memory)? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are using Kong with KIC and Postgres DB.
Kong - 2.7.1
KIC - 2.2.1
We have two Kong deployments in two different data centers which are pointing to same Postgres DB.
DC1 - Kong and Postgres
DC2 - Kong
We are getting below error continuously in KIC in DC2 -
Also we have below environment variable set in KIC -
proxy_timeout_seconds: 120
What we can do to resolve this error? Do we need to further increase the timeout values?
Beta Was this translation helpful? Give feedback.
All reactions