Sites won't help here because of 2 reasons:
1. You start up the AD site discovery process sequentially connecting to ALL DCs that are
registered in SRV. This has to be done this way as you do not know yet to which site you
belong to.
If the random DC you pick up responds, you're lucky and you can finish the discovery
process and discover the site you belong to.
If you are unlucky, the DC is unresponsive and you'll end up with AD provider
offline.
2. Once you discovered the site, there is still the risk that some DCs defined for the
site will be down or unresponsible - so the scenario above can happen as well.
Moreover it seems to me that SSSD is doing the site discovery too often. It should be done
once SSSD starts up or if we spot the IP address change - there is no reason to do it
otherwise. Nowadays I see it in logs on a regular basis.
Ondrej
To me, this is really serious problem which renders the service
discovery feature actually unusable.
Ondrej
I see your point, but wouldn't this be solvable better with sites? ie only advertise
those DCs that the client can actually use rather than working around it on the client
side?
_______________________________________________
sssd-users mailing list
sssd-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-users
-----
The information contained in this e-mail and in any attachments is confidential and is
designated solely for the attention of the intended recipient(s). If you are not an
intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or
any part thereof. If you have received this e-mail in error, please notify the sender by
return e-mail and delete all copies of this e-mail from your computer system(s). Please
direct any additional queries to: communications(a)s3group.com. Thank You. Silicon and
Software Systems Limited (S3 Group). Registered in Ireland no. 378073. Registered Office:
South County Business Park, Leopardstown, Dublin 18.