Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support round-robin in fail over #3885

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Support round-robin in fail over #3885

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2844


Currently we choose a server, connect to it and then keep using it until the server breaks. This is fine in general, but some users would prefer if the connection was more short-lived (configurable lifetime) and if sssd choose one of the servers at random.

Comments


Comment from jhrozek at 2015-10-20 12:48:07

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1273384

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1273384 1273384]


Comment from jhrozek at 2015-10-21 13:36:01

Not needed in the immediate future, I think the defer bucket would be OK.


Comment from jhrozek at 2015-10-22 17:28:31

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred


Comment from jhrozek at 2017-02-24 14:27:43

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD Patches welcome

Comment from pbrezina at 2020-03-24 14:17:04

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.


Comment from pbrezina at 2020-03-24 14:17:05

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant