Learn more about these different git repos.
Other Git URLs
In the event that an SBUS service dies, any other SSSD service that relies on this connection needs to be able to reconnect to it once the service restarts. Additionally, we want the clients to be able to queue their requests until the service is available again, so that no data loss occurs (unless the client reaches its timeout).
Working on this issue.
Current progress: I have implemented the reconnection logic and tested it on the Data Provider <--> Backend connections.
Still to do: NSS and PAM connections to the Data Provider.
status: new => assigned
Fields changed
component: Service Monitor => SBUS
Fixed by commits - [6a3ca34] - Add reconnection logic to the SBUS - [76c4a8c] - Enable autoreconnection of Data Provider Backends to the Data Provider
resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to sgallagh - Issue set to the milestone: Iteration 2
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/1044
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.