Hi Bren, On Sat, Nov 29, 2025 at 07:36:53PM +0000, Bren wrote: > On Friday, September 26th, 2025 at 11:26 AM, Bren <[email protected]> > wrote: > > > > > > > Hello, > > > > We used to sync some stick tables on reload like this: > > > > peers local > > peer server 127.0.0.1:10000 > > > > That was really slick. Now we've moved to using bind with SSL and I haven't > > been able to replicate the above setup. > > > > peers synced > > bind server:83 ssl crt cert.pem > > server server1 > > server server2 IP:83 sni server2.domain.net > > server server3 IP:83 sni server3.domain.net > > > > Any way to sync stick tables to the local process on reload when using > > bind? We have some million+ tables that get flushed on reload so this would > > be real handy. > > This appears to have started to work again after updating to 3.2.9. I wonder > if this had anything to do with it: > > - stick-tables had two issues: one by which a local update was not always > propagated to peers if the entry had been received from them first, and > another one where the refcount of an entry can become inconsistent and > prevent the entry from ever expiring if a local and remote update happen at > the exact same time and the local entry is created at the moment the peers > code releases the lock. > > I haven't made any other changes to the peers config since I last looked at > this. This is a nice surprise.
Normally it is expected to work, so if it didn't, it was likely due to a bug. A few ones were fixed recently in the way stick-table updates are propagated to peers. I can't designate a specific one that could have caused your problem but it's very possible that you've been hit by one of them. Please continue to watch in case the problem happens again. And next time do not hesitate to ping again if you don't get any response after a few days; it just means everyone's busy and your message wasn't noticed. Willy
