Re: [PATCH] do_reconnect: expiry check of dclist BEFORE lookup using it
Patrick Cernko <[email protected]> Fri, 27 Feb 2026 08:22:54 +0100
| Newsgroups | org.kernel.vger.autofs |
|---|---|
| Organization | Gemeinsame Einrichtungen der MPIs KL und SB |
| Message-ID | <[email protected]> |
Hi autofs developers, it's been quiet a while since I submitted this patch but I never got any feedback if it was accepted or rejected. Is there something wrong with my submission or didn't you have time yet to review it. On 2025-10-02 12:52:49, Patrick Cernko wrote: > Hi autofs developers, > > this patch changes the behavior when to refresh LDAP SRV records. The > documentation states: > >> The server list returned from an SRV RR lookup is refreshed according >> to the minimum ttl found in the SRV RR records or after one hour, >> whichever is less. > > But the code in fact does not do any refreshing as long as at least one > server in the dclist still responds. > > This issue became obvious in our setup, when we had to disable the first > two servers: autofs continued to contact ldap-a and ldap-b, running in > timeouts (~5sec) and finally got an answer from ldap-c. But due to the > timeouts every mount took >10sec resulting in slow responsiveness for > the whole system. Changing the SRV records (with TTLs of 7200) did not > help. As a workaround we had to signal all client's automount processes > with HUP. > > The change invalidates the dclist if expired. This forces autofs to do a > new SRV record lookup before doing the LDAP lookup. > > Best regards, Best regards, -- Patrick Cernko <[email protected]> +49 681 9325 5815 Joint Scientific IT and Technical Service Max-Planck-Institute für Informatik & Software Systems
smime.p7s
(application/pkcs7-signature, 4.8 KB) - not displayed