Skip to main content
Question

Idle session timeout being automatically set as 10 seconds

  • May 10, 2024
  • 7 replies
  • 10 views
vaishnavav99
Forum|alt.badge.img+1

I recently upgraded Vertica to v23.4. Now I am seeing the following error in my application.
"Failed to connect to xxxxx on host x.x.x.x, port 5433. Reason: FATAL: Session idle for more than 10000 ms. Session Timed Out!
"

I checked vertica.log files and could see the following
"[Session] Set idle timeout for remote host y.y.y.y to 00:00:10" which confirms the idle session for this host is being set as 10 seconds.

In the same logs it is declaring the idle session timeout for the user correctly

2024-05-10 06:10:31.331 Init Session:0x7fbfc8d0a700 @v_vertica_qa_node0001: 00000/7400: Current idle session timeout = 01:00

We have not configured 10 seconds timeout in the user, DB or node level. The idle session timeout configured as default is UNLIMITED and the idle session timeout for this specific user is 1 Hour.

In verticas that are not v23.4, I am not seeing the log line which says "Set idle timeout for remote host ..."

Is this 10 seconds, default value for vertica v23.4 ? Or is this related to the client being used ?

    7 replies

    vaishnavav99
    Forum|alt.badge.img+1
    • vaishnavav99
    • Author
    • Participating Frequently
    • May 13, 2024

    Any idea on this ?

    Bryan_H
    Forum|alt.badge.img+2
    • Bryan_H
    • Participating Frequently
    • May 13, 2024

    By "unlimited", do you mean that no value is set at the DB level according to "select * from configuration_parameters where parameter_name = 'DefaultIdleSessionTimeout';"
    Recommend you open a support case as there are multiple client and server setting that could affect session or socket timeout in 23.4.

    vaishnavav99
    Forum|alt.badge.img+1
    • vaishnavav99
    • Author
    • Participating Frequently
    • May 14, 2024

    Any idea on this ?> @Bryan_H said:

    By "unlimited", do you mean that no value is set at the DB level according to "select * from configuration_parameters where parameter_name = 'DefaultIdleSessionTimeout';"
    Recommend you open a support case as there are multiple client and server setting that could affect session or socket timeout in 23.4.

    Thank you for responding @Bryan_H

    Above shows the DefaultIdleSessionTimeout value for the DB. This is the same as what I have for DBs which are not upgraded to v23

    select * from v_catalog.users shows idlesessiontimeout as 'unlimited' for all users

    SruthiA
    Forum|alt.badge.img+1
    • SruthiA
    • Participating Frequently
    • May 14, 2024

    @vaishnavav99 : As mentioned by Byran, please open a support case. there are many variations to it.

    Bryan_H
    Forum|alt.badge.img+2
    • Bryan_H
    • Participating Frequently
    • May 14, 2024

    Also check the setting "IdleTimeoutInitializingConnectionsMs" which defaults to 10000 ms (10 seconds). This is idle timeout waiting for client connection, and it seems unusual that the client would take longer than 10 seconds to establish connection. You can set this to a longer time, or 0 to disable, but then you might have hanging or unresponsive client sessions that are not automatically closed.

    vaishnavav99
    Forum|alt.badge.img+1
    • vaishnavav99
    • Author
    • Participating Frequently
    • May 16, 2024

    @Bryan_H said:
    Also check the setting "IdleTimeoutInitializingConnectionsMs" which defaults to 10000 ms (10 seconds). This is idle timeout waiting for client connection, and it seems unusual that the client would take longer than 10 seconds to establish connection. You can set this to a longer time, or 0 to disable, but then you might have hanging or unresponsive client sessions that are not automatically closed.

    Thanks @Bryan_H I will explore this config. Looks like it is not present in the older versions of Vertica but in 23.4 it is present. That might explain it. I will test it out and let you know how it went.

    vaishnavav99
    Forum|alt.badge.img+1
    • vaishnavav99
    • Author
    • Participating Frequently
    • May 16, 2024

    Thanks @Bryan_H. That config seems to be behind this message. Thanks for guiding.

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement