eolivelli commented on pull request #2435: URL: https://github.com/apache/bookkeeper/pull/2435#issuecomment-708992769
If you simply upgrade an existing cluster from 4.9/10/11 to 4.12 everything will work well. You can set enableBookieAddressTracking=false safely as bookies are using hostname:port as bookieId and it is not expected that this address changes. I am setting enableBookieAddressTracking=true by default because I think this is the future for BK and also in order to have all tests working with this feature. The case of enableBookieAddressTracking=false is to save resources on ZK, by reducing the number of watcher. If we were on ZK 3.6.x (client + server) we could leverage "Persistent Recursive Watches", that is a single watch for an entire tree of znodes, without the need to set it again after it triggers, and this will also mitigate the impact of these new additional watches ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
