Learn more about these different git repos.
Other Git URLs
Currently when SSSD marks a server as unavailable, it will ignore it until all other servers have failed before it will retry the 1st in the list.
I would like to request that sssd rechecks the status of the 1st server in the list as its primary and returns to using it when it is discovered functional again.
Otherwise, the recovery of a primary server requires that an entire data center restart their sssd daemon to return back to the first server in the sssd.conf
component: SSSD => Failover
milestone: NEEDS_TRIAGE => SSSD 1.9.0 NEEDS_TRIAGE
"Nice to have" for 1.9.
milestone: SSSD 1.9.0 NEEDS_TRIAGE => SSSD 1.9.0
milestone: SSSD 1.9.0 => SSSD Preferred Servers
milestone: SSSD Preferred Servers => SSSD 1.10 beta
I had some thoughts on how to resolve this. We should probably implement two failover lists: one that is a list of preferred servers and the other that is a list of backup servers.
If any of the preferred servers can be contacted, we will maintain this connection until we no longer can. If we are disconnected, we will always try all of the preferred servers before falling to the backup servers.
While we are connected to a backup server, we should try at a configurable interval to reconnect to one of the primary servers.
This functionality should be modular internally, so that we can potentially support auto-detecting primary servers and secondary servers in the future (e.g. location-awareness).
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=789470
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=789470 789470]
milestone: SSSD 1.10 beta => SSSD 1.9.0 beta 3
owner: somebody => jzeleny
status: new => assigned
milestone: SSSD 1.9.0 beta 6 => SSSD 1.9.0 beta 7
patch: 0 => 1
milestone: SSSD 1.9.0 beta 7 => SSSD 1.9.0 beta 6
resolution: => fixed
status: assigned => closed
Metadata Update from @jraquino:
- Issue assigned to jzeleny
- Issue set to the milestone: SSSD 1.9.0 beta 6
to comment on this ticket.