#1128 Introduce the concept of a Primary Server in SSSD
Closed: Fixed None Opened 10 years ago by jraquino.

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

Fields changed

component: SSSD => Failover

Fields changed


"Nice to have" for 1.9.

milestone: SSSD 1.9.0 NEEDS_TRIAGE => SSSD 1.9.0

Fields changed

feature_milestone: =>
milestone: SSSD 1.9.0 => SSSD Preferred Servers

Fields changed

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).

Fields changed

milestone: SSSD 1.10 beta => SSSD 1.9.0 beta 3

Fields changed

owner: somebody => jzeleny
status: new => assigned

Fields changed

milestone: SSSD 1.9.0 beta 6 => SSSD 1.9.0 beta 7

Fields changed

patch: 0 => 1

- 75ee792
- bbd33e4
- 10922e0
- 1ecdcf6
- b418d3b
- d7e3035
- 016e0d7
- 9da182c
- f6cd123
- 07b7b76
- 46118ee
- 294e9a5

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

5 years ago

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/2170

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.