Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

The Definitive HDFS Service Start/Stop Checklist for Cloudera Clusters

avatar
New Member

In a typical HDFS HA deployment, Zookeeper, ZKFailoverController, DataNodes, NameNodes and JournalNodes, are all installed. What's the best order of starting/stoping these HDFS services to avoid running into services dependency issues?

1 ACCEPTED SOLUTION

avatar

You need to follow the below Start order

  • Ranger
  • Knox
  • ZooKeeper
  • HDFS
    • Journal Node
    • Name Node
    • Secondary Name Node
    • Data Node
  • YARN
    • Resource Manager
    • History Server
    • Node Manager

View solution in original post

4 REPLIES 4

avatar
Master Guru

Stop order:

1. Stop Datanodes

2. Stop Namenodes

3. Stop ZKs

4. Stop Journal nodes

Start Order:

1. Start ZKs

2. Start JNs

3. Start Datanodes

4. Start NNs

avatar

If you are using ambari , It will take care of the sequence. You just need to click on start service and start service.

avatar

You need to follow the below Start order

  • Ranger
  • Knox
  • ZooKeeper
  • HDFS
    • Journal Node
    • Name Node
    • Secondary Name Node
    • Data Node
  • YARN
    • Resource Manager
    • History Server
    • Node Manager

avatar
New Member

Thank you all for the answers.