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]

Cloudera Community

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this topic

Journal Node Sync - moving to new machine

avatar
author-rank kartikbha
Rising Star

Created on ‎11-08-2016 03:48 AM - edited ‎09-16-2022 03:46 AM

We have three journal nodes. One was creating issue of sync with name node. Even after multiple rolling restart did not fix sync issue.

 

Later we moved, Journal node services to another node but we again got sync issue with new host’s - journal node to name node.

 

Another things observed here is, location /Data0/dfs/jn directory was empty on new journal node host after moving one journal node service there.

 

Restart of Zookeeper & Journal node did not enable creation of edit logs on new host as well. We have also tried to move everything from working/old JN's location /Data0/dfs/jn/hanameservice/* to new host as per below section.

https://www.cloudera.com/documentation/enterprise/5-4-x/topics/cm_mc_jn.html

 

Can you please suggest, how to enable sync of Journal node with namenode or what step actually we are missing here?

 

CDH - 5.4.+

 

 

Regards,

Kartik

19,357
1
Who agreed with this topic