Member since
08-08-2017
1652
Posts
30
Kudos Received
11
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1574 | 06-15-2020 05:23 AM | |
11372 | 01-30-2020 08:04 PM | |
1732 | 07-07-2019 09:06 PM | |
7178 | 01-27-2018 10:17 PM | |
4011 | 12-31-2017 10:12 PM |
12-12-2024
10:08 AM
1 Kudo
@irshan When you add balancer as a role in the HDFS cluster, it indeed will show as not started. So its an expected one. Coming to your main query, it could be possible that when you run the balancer, the balancer threshold could be with in the default percentage of 10, so it won't move the blocks. You may have to reduce the balance threshold and try again.
... View more
11-15-2024
11:50 PM
1 Kudo
@mike_bronson7 these messages indicates that the Controller is being elected on other node and the current broker who is acting as a controller initiating a clean shutdown to handover the controller responsibilities to the newly elected controller. These messages are normal, but if you are facing frequent controller failures / elections / controller switches to other nodes then this could be a concern. As long as if this is happening for a genuine reason such as Cluster restart / controller broker restarts. This is valid. Also, if the Controller broker disconnects from Zookeeper and looses the Controller Znode then the other brokers participate on controller election, that would also trigger these messages
... View more
04-21-2024
11:30 PM
Hi, @mike_bronson7 did you try to delete the host from Ambari UI? if not please try that out first. You might need to stop the ambari server first delete entries from the backed DB commit the changes then start your ambari server. But I would recommend deleting if from Ambari UI and checking.
... View more
04-17-2024
03:10 PM
1 Kudo
I was looking for the same info and found that great link below. https://hadoop.apache.org/docs/current/hadoop-distcp/DistCp.html I hope it can help you. Best,
... View more
04-16-2024
11:59 PM
1 Kudo
Hi @mike_bronson7 Please check that if the RM is working fine or is it down. Please also check your zookeeper. Please check with telnet if you can connect to RMhost from other host.
... View more
03-20-2024
11:46 PM
1 Kudo
thank you for response but look on that also 2024-03-18 19:31:52,673 WARN datanode.DataNode (BlockReceiver.java:receivePacket(701)) - Slow BlockReceiver write data to disk cost:756ms (threshold=300ms), volume=/data/sde/hadoop/hdfs/data 2024-03-18 19:35:15,334 WARN datanode.DataNode (BlockReceiver.java:receivePacket(701)) - Slow BlockReceiver write data to disk cost:377ms (threshold=300ms), volume=/data/sdc/hadoop/hdfs/data 2024-03-18 19:51:57,774 WARN datanode.DataNode (BlockReceiver.java:receivePacket(701)) - Slow BlockReceiver write data to disk cost:375ms (threshold=300ms), volume=/data/sdb/hadoop/hdfs/data As you can see the warning is also on local disks not only across the network In any case we already checked the network include the switches and we not found a problem Do you think its could be tuning issue in hdfs parameters or some parameters that can help
... View more
02-27-2024
12:29 AM
2 Kudos
Yes @mike_bronson7 above steps also works
... View more
02-05-2024
05:21 AM
1 Kudo
=> If above steps still gives you issues then you can simply execute step 5 or below Cmd from Standby NN // Bootstrap Standby NameNode. This command copies the contents of the Active NameNode's metadata directories (including the namespace information and most recent checkpoint) to the Standby NameNode. # hdfs namenode -bootstrapStandby Note: Step 1 to step 3 is process of creating new fsimage but if your Active NN is already up and running then I would directly login in to Standby and then perform bootstrapStandby operation
... View more
11-12-2023
07:47 PM
fix: `componentname` should be `component_name`
... View more