Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

Ambiguity of config session_idle_timeout_secs #1242

Closed
jievince opened this issue Jul 12, 2021 · 1 comment
Closed

Ambiguity of config session_idle_timeout_secs #1242

jievince opened this issue Jul 12, 2021 · 1 comment

Comments

@jievince
Copy link
Contributor

It seems that config session_idle_timeout_secs set the max idle time of the session. But actually, it records the time since a session is created, even if the session is not idle(eg. executing queries).

Reproduce:
set session_idle_timeout_secs to 10s, and then execute a slow query. After session_idle_timeout_secs and at next session_reclaim_interval_secs, the query will be killed

@CPWstatic
Copy link
Contributor

session_reclaim_interval_secs, nebula will try to reclaim sessions every session_reclaim_interval_secs.
session_idle_timeout_secs , nebula will count the idle time of session, if the real idle time greater than session_idle_timeout_secs, nebula will expires it at the next period of session_reclaim_interval_secs.

We will not kill the query actively, unless users demands it explicitely.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants