Learn more about these different git repos.
Other Git URLs
Currently we have a simple single 5 minutes timeout for clients. If sssd_nss or sssd_pam are stuck the client will have to wait a full 5 minutes before giving up.
We can change the strategy to use a series of pings instead. This will require adding a new request type to the client and handling the fact sssd_nss/pam may reply to the actual request before replying to the ping.
But at least this would allow to quickly detect stuck daemons. The ping could be sent every 10 seconds awith a timeout of a few (say 5) seconds. This way if sssd_nss is stucck the client will not wait more then 15 seconds.
After some discussion we've came to the conclusion that it is not necessary for the client to ping the responder, because there is already a ping from the monitor. The monitor will kill the responder if it is stuck which closes the connection for the client.
resolution: => invalid status: new => closed
Fields changed
rhbz: => 0
milestone: NEEDS_TRIAGE => void
Metadata Update from @simo: - Issue set to the milestone: void
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/1729
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.