Learn more about these different git repos.
Other Git URLs
This might be useful in environments like compute clusters where it's likely that all nodes are brough up at the same time, then the subdomain task connects an all nodes which means the expiry timeout and the reconnection also happen during the same time.
The easy thing to do is to randomize the lifetime. A harder, but potentially nicer thing do to might be to instead of leaving the connection expire and then reconnect is to randomly select a time between say 75% of the connection lifetime and the expiry and reconnect proactively.
Metadata Update from @jhrozek: - Issue tagged with: RFE, performance
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.0
Metadata Update from @jhrozek: - Issue priority set to: minor
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1583592
Issue linked to Bugzilla: Bug 1583592
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Metadata Update from @thalman: - Issue assigned to thalman
PR: https://github.com/SSSD/sssd/pull/951
Metadata Update from @atikhonov: - Issue tagged with: PR
master
Metadata Update from @pbrezina: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
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/4651
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.