bryancall commented on issue #11724:
URL: 
https://github.com/apache/trafficserver/issues/11724#issuecomment-4828155726

   This was fixed by [PR 
#12892](https://github.com/apache/trafficserver/pull/12892) (the configuration 
reload token model). The root cause was exactly as described here: 
`SSLClientCoordinator::startup()` used a `ConfigUpdateHandler` and called 
`attach()` once per record, so the reconfigure callback fired independently for 
each changed SSL config file, producing duplicate reloads. That PR replaced the 
per-record attach mechanism with a single coordinated registration 
(`ConfigRegistry::register_record_config` under the key 
`ssl_client_coordinator`), so the reconfigure handler now runs once per reload 
regardless of how many SSL files changed. The follow-up [PR 
#13075](https://github.com/apache/trafficserver/pull/13075) added a 
`Test.AddConfigReload()` autest extension covering reload behavior. For 
reference, [PR #11723](https://github.com/apache/trafficserver/pull/11723) was 
a separate QUIC reload bug found while investigating this one and is not the 
fix here. The fix is on the master 
 branch and is scheduled for the 11.0.0 release. Closing as resolved.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to