问题
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?
EDIT
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
- 3 Hbase Master (1 Active & 2 standby)
- 4 Region Servers
- 4 Data Nodes
- 1 Primary & 1 Secondary Name Node
- 3 Journal Node
- 4 Nodemanager
- 3 Resource Manager (1 Active & 2 standby)
What should be the order of stopping, upgrading & starting of components? Is it like below:-
- Stop, Upgrade & Start all data nodes one by one.
- Stop, Upgrade & Start region servers one by one
- Stop, Upgrade & Start Upgrade HBase standby nodes one by one
- Stop, Upgrade & Start Secondary Name Node
- Upgrade Primary Name Node
- Upgrade Journal Nodes
- Upgrade HBase Master
- Stop, upgrade & Start standby Resource Manager one by one
- Stop, upgrade & Start Active Resource Manager
- 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?
回答1:
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:
- 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
- Backup Cloudera Manager database
- Upgrade Cloudera Manager server
- Upgrade Cloudera Manager Agents on all hosts
- Upgrade CDH parcels
- 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.
If you are not using Cloudera Manager, you will have to go through the command line upgrade procedures.
- Before Upgrading to the Latest Release of CDH
- Upgrade CDH to latest
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.
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 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
来源：https://stackoverflow.com/questions/47660125/cdh-community-edition-rolling-upgrade-from-5-7-to-5-13