clintropolis commented on issue #10780: URL: https://github.com/apache/druid/issues/10780#issuecomment-763364916
>What would the migration path look like? Would people need to update Druid and their ZK quorum in a specific order or would various orders works? Any downtime needed? I am assuming since newer client libs do not support 3.4.x that we would announce deprecation while continuing to use the existing client libs, to give time for operators to migrate clusters to 3.5.x. So, (if I understand correctly) the path initially would only involve upgrading ZK, which I would think could be done out of band with any Druid updates. Assuming this is correct, I think this should be relatively low risk to encourage cluster operators to upgrade their ZK cluster to 3.5.x (other than the risk of doing the upgrade of course); my anecdotal evidence for this being that I have been using it locally for all of my testing since shortly after 3.5.x became a 'stable' branch and haven't ran into any issues using the current set of client libraries. >But I'm not sure if this refers to a 3.4.x client or a 3.4.x server (or both). Based on [this comment in our pom.xml](https://github.com/apache/druid/blob/master/pom.xml#L116) about zk version, I assume client libraries? ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
