#3835 KCM: Increase the default client idle timeout, consider decreasing the timeout on busy servers
Closed: cloned-to-github 2 years ago by pbrezina. Opened 3 years ago by jhrozek.

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?)


Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

3 years ago

Metadata Update from @jhrozek:
- Issue priority set to: critical (was: minor)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

2 years ago

Metadata Update from @thalman:
- Issue tagged with: Future milestone

2 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4829

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata