CDH Community Edition从5.7滚动升级到5.13 [英] CDH Community Edition Rolling Upgrade from 5.7 to 5.13

问题描述

有人可以让我知道如何执行CDH从5.7到5.13的滚动升级吗？在Cloudera文档中找不到有关CDH社区版滚动升级的内容吗？

Can someone let me know how can I perform Rolling Upgrade of CDH from 5.7 to 5.13? I could not find much in Cloudera documentation regarding rolling upgrade of CDH Community Edition?

编辑

按照下面的讨论，我可以手动停止，升级（通过 1单击安装）和启动节点来进行升级。在下面的群集中

As per the discussion below I can do upgrades manually stopping, upgrading (via "1 Click Install" )and starting the nodes. In a cluster like below

1. 3 Hbase Master（1个活动和2个备用数据库）


2. 4区域服务器


3. 4个数据节点


4. 1个主& 1次要名称节点


5. 3日记节点


6. 4 Nodemanager


7. 3资源管理器（1个活动& 2备用）

1. 3 Hbase Master (1 Active & 2 standby)
2. 4 Region Servers
3. 4 Data Nodes
4. 1 Primary & 1 Secondary Name Node
5. 3 Journal Node
6. 4 Nodemanager
7. 3 Resource Manager (1 Active & 2 standby)

停止，升级和升级的顺序应该是什么？组件启动？是否如下所示：-

What should be the order of stopping, upgrading & starting of components? Is it like below:-

1. 停止，升级和升级


2. 停止，升级并升级所有数据节点。依次启动区域服务器


3. 停止，升级和升级；逐步开始升级HBase备用节点


4. 停止，升级和升级；启动辅助名称节点


5. 升级主名称节点


6. 升级日志节点


7. 升级HBase主节点


8. 停止，升级和升级逐一启动待机资源管理器


9. 停止，升级和升级；启动Active Resource Manager


10. 停止，升级和升级

1. Stop, Upgrade & Start all data nodes one by one.
2. Stop, Upgrade & Start region servers one by one
3. Stop, Upgrade & Start Upgrade HBase standby nodes one by one
4. Stop, Upgrade & Start Secondary Name Node
5. Upgrade Primary Name Node
6. Upgrade Journal Nodes
7. Upgrade HBase Master
8. Stop, upgrade & Start standby Resource Manager one by one
9. Stop, upgrade & Start Active Resource Manager
10. Stop, Upgrade & Start Nodemanagers one by one.

如果我不遵循任何命令并并行更新节点中的服务，我会面对吗？有什么问题（因为这只是次要版本升级）？

If I don't follow any order and update the services in the nodes in parallel, will I face any issue (as this is just a minor version upgrade)?

如果我通过停止所有节点中的所有服务并升级然后启动来关闭整个群集？启动服务时应该遵循什么顺序？

If I am taking the entire cluster down by stopping all the services in all the nodes and upgrading and then starting? What order should I follow while starting the services?

推荐答案

我认为您必须手动执行此操作，因为您正在使用社区版本。

I think you have to do it manually since you are using Community Version.

滚动升级允许您升级群集软件，而
可以在不使群集脱机的情况下重新启动升级的服务。
执行滚动升级需要执行以下操作：

A rolling upgrade allows you to upgrade your cluster software and restart the upgraded services without taking the cluster offline. Performing a rolling upgrade requires the following:

• 已使用Cloudera Manager和包裹安装了CDH。您可以将群集从使用软件包迁移到使用包裹。


• 群集使用Cloudera Enterprise许可证。

• CDH was installed using Cloudera Manager and parcels. You can migrate your cluster from using packages to using parcels.
• The cluster uses a Cloudera Enterprise license.

升级概述页面具有您所需的信息，但通常遵循

The upgrade overview page has the information you need, but it generally follows

1. 备份Cloudera Manager数据库
>

2. 升级Cloudera Manager服务器


3. 升级所有主机上的Cloudera Manager代理


4. 升级CDH包裹


5. 重新启动群集。尝试按服务进行操作。例如，在启动Hadoop服务之前，请确保所有Cloudera代理运行状况良好。然后启动namenode和datanode，然后启动resourcemanager等。

1. Backup Cloudera Manager database
2. Upgrade Cloudera Manager server
3. Upgrade Cloudera Manager Agents on all hosts
4. Upgrade CDH parcels
5. Reboot cluster. Try to do it per service. For example, make sure all Cloudera agents are healthly before starting Hadoop services. Then start the namenode(s), and datanodes, followed by resourcemanager(s), etc.

如果您不使用Cloudera Manager ，则必须执行命令行升级过程。

If you are not using Cloudera Manager, you will have to go through the command line upgrade procedures.

• 升级到CDH的最新版本之前


• 将CDH升级到最新

• Before Upgrading to the Latest Release of CDH
• Upgrade CDH to latest

会在做任何事情之前停止所有服务。例如，如果数据节点和名称节点关闭，则HBase将无法正常工作。

From those you listed, you would stop all services before doing anything. For example, HBase isn't going to work if the datanodes and namenodes are down.

构建一个依赖关系树，并将其从最依赖的服务中关闭。意思是，关闭HBase，然后关闭YARN（一次一个资源管理器），然后关闭HDFS（数据节点，然后是名称节点和journalnode）。然后升级并以相反的顺序启动它们。

Build a dependency tree, and shut it down from the most dependent services. Meaning, HBase off, then YARN (one resource manager at a time), then HDFS (datanodes, then namenodes and journalnodes). Then upgrade and start them in reverse order.

那里的第二个链接说此升级顺序

The second link there says this order for upgrades

• NameNode进入安全模式


• 停止所有Hadoop服务


• 备份namenode


• 下载一键式软件包


• 升级YARN（需要升级Zookeeper）


• 升级JournalNodes


• 开始HDFS服务


• 启动YARN


• 升级其余组件

• NameNode into safemode
• Stop all Hadoop services
• Backup the namenode
• Download the 1-click packages
• Upgrade YARN (which requires upgrading Zookeeper)
• Upgrade JournalNodes
• Start HDFS Service
• Start YARN
• Upgrade rest of components

这篇关于CDH Community Edition从5.7滚动升级到5.13的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！