URL:
https://github.com/SSSD/sssd/pull/752
Author: pbrezina
Title: #752: sbus: terminated active ongoing request when reconnecting
Action: opened
PR body:
"""
Connection to the remote dbus server was lost. If there are any outgoing
requests they are waiting for a pretty long timeout. During this timeout
we kept chaining even new requests that come after successful reconnection
and these request were waiting for the timeout to ocurr as well because
they were chain to request that started before reconnection.
Now, we terminated all active outgoing request that have a key associated
so we can immediately start sending new requests.
Resolves:
https://pagure.io/SSSD/sssd/issue/3907
This is a trivial solution for now. It would be also possible to resend
existing request after reconnection so their consumers may get correct
answer. This however requires some logic behind in order to detect requests
that actually are causing the crash to avoid endless crash loop of sssd.
I'm thinking on - retry once, if sssd crashes again then kill the request.
Should I create a ticket for this?
"""
To pull the PR as Git branch:
git remote add ghsssd
https://github.com/SSSD/sssd
git fetch ghsssd pull/752/head:pr752
git checkout pr752