将 Zookeeper 从 3.3.X 升级到 3.4.X 时我需要知道什么? [英] What do I need to know when upgrading Zookeeper from 3.3.X to 3.4.X?

问题描述

我有一个 Zookeeper 集成，我想从 3.3.X 升级到 3.4.X 分支.这可以在实时集群上完成吗?需要停机吗?有什么可以在某处找到的说明吗?

解决方案

从我查到的，

<块引用>

6. 升级 ZooKeeper 的选项/过程是什么?

有两种主要方法可以做到这一点；1) 完全重启或 2) 滚动重启.

在完全重启的情况下，您可以暂存更新的代码/配置/等...，停止集合中的所有服务器，切换代码/配置，然后重新启动 ZooKeeper 集合.如果您以编程方式(通常是脚本，即不是手动)执行此操作，则可以在几秒钟内完成重新启动.因此，在此期间，客户端将失去与 ZooKeeper 集群的连接，但在客户端看来，它就像一个网络分区.一旦 ZooKeeper 集合恢复，所有现有的客户端会话都会被维护和重新建立.显然，这种方法的一个缺点是，如果您遇到任何问题(在测试工具上测试/暂存这些更改总是一个好主意)，集群可能会停机的时间比预期的要长.对于许多用户来说，第二种选择是滚动重启".在这种情况下，您一次升级 ZooKeeper 集合中的一台服务器；关闭服务器，升级代码/配置/等...，然后重新启动服务器.服务器将自动重新加入仲裁，使用当前 ZK 领导者更新其内部状态，并开始为客户端会话提供服务.由于执行滚动重启而不是完全重启，管理员可以在升级过程中监控整体，如果遇到任何问题，可能会回滚

我认为您需要下载文件并解压到本地文件夹并将配置文件/设置传输到新版本，然后关闭旧服务器并运行新版本服务器

https://wiki.apache.org/hadoop/ZooKeeper/FAQ

I have a Zookeeper ensemble I'd like to upgrade from 3.3.X to 3.4.X branch. Can this be done on a live cluster? Requires downtime? Are there any instructions to be found on this somewhere?

解决方案

From what I checked ,

6. What are the options/process for upgrading ZooKeeper?

There are two primary ways of doing this; 1) full restart or 2) rolling restart.

In the full restart case you can stage your updated code/configuration/etc..., stop all of the servers in the ensemble, switch code/configuration, and restart the ZooKeeper ensemble. If you do this programmatically (scripts typically, ie not by hand) the restart can be done on order of seconds. As a result the clients will lose connectivity to the ZooKeeper cluster during this time, however it looks to the clients just like a network partition. All existing client sessions are maintained and re-established as soon as the ZooKeeper ensemble comes back up. Obviously one drawback to this approach is that if you encounter any issues (it's always a good idea to test/stage these changes on a test harness) the cluster may be down for longer than expected. The second option, preferable for many users, is to do a "rolling restart". In this case you upgrade one server in the ZooKeeper ensemble at a time; bring down the server, upgrade the code/configuration/etc..., then restart the server. The server will automatically rejoin the quorum, update it's internal state with the current ZK leader, and begin serving client sessions. As a result of doing a rolling restart, rather than a full restart, the administrator can monitor the ensemble as the upgrade progresses, perhaps rolling back if any issues are encountered

I am thinking you need to download the file and extract to a local folder and transfer the configuration file/settings into the new version and have the old server down and run the new version server

https://wiki.apache.org/hadoop/ZooKeeper/FAQ

这篇关于将 Zookeeper 从 3.3.X 升级到 3.4.X 时我需要知道什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！