You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
By default, KCM has a 60-second idle client timeout. This might not be enough, because the client is often kinit, so there is some user interaction involved.
We should increase the timeout. But we should also consider decreasing it if the server is too busy (say, over half of the maximum fds are depleted?)
By default, KCM has a 60-second idle client timeout.
This might not be enough, because the client is often kinit,
so there is some user interaction involved.
Verifies: #4829
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1884205
Reviewed-by: Madhuri Upadhye <mupadhye@redhat.com>
akuster
pushed a commit
to akuster/sssd
that referenced
this issue
May 18, 2021
By default, KCM has a 60-second idle client timeout.
This might not be enough, because the client is often kinit,
so there is some user interaction involved.
Verifies: SSSD#4829
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1884205
Reviewed-by: Madhuri Upadhye <mupadhye@redhat.com>
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3835
By default, KCM has a 60-second idle client timeout. This might not be enough, because the client is often kinit, so there is some user interaction involved.
We should increase the timeout. But we should also consider decreasing it if the server is too busy (say, over half of the maximum fds are depleted?)
Comments
Comment from jhrozek at 2018-09-27 11:43:00
Metadata Update from @jhrozek:
Comment from jhrozek at 2018-10-03 14:36:48
Metadata Update from @jhrozek:
Comment from jhrozek at 2019-02-22 15:22:36
Metadata Update from @jhrozek:
Comment from jhrozek at 2019-06-13 23:11:02
Metadata Update from @jhrozek:
Comment from thalman at 2020-03-11 12:27:46
Metadata Update from @thalman:
The text was updated successfully, but these errors were encountered: