One Hat Cyber Team

Your IP: 216.73.216.94
Server IP: 178.33.27.10
Server: Linux cpanel.dev-unit.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Server Software: Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
PHP Version: 8.2.11
Buat File | Buat Folder

Dir : ~/usr/local/src/netdata/health/guides/hdfs/

View File Name : hdfs_dead_nodes.md

### Understand the Alert

The Netdata Agent monitors the number of DataNodes that are currently dead. Receiving this alert indicates that there are dead DataNodes in your HDFS cluster. The NameNode characterizes a DataNode as dead if no heartbeat message is exchanged for approximately 10 minutes. Any data that was registered to a dead DataNode is not available to HDFS anymore.

This alert is triggered into critical when the number of dead DataNodes is 1 or more.

### Troubleshoot the Alert 

1. Fix corrupted or missing blocks.

    ```
    root@netdata #  hadoop dfsadmin -report
    ```

    Inspect the output and check which DataNode is dead.

2. Connect to the DataNode and check the log of the DataNode. You can also check for errors in the system services.

    ```
    root@netdata #  systemctl status hadoop
    ```

   Restart the service if needed.


3. Verify that the network connectivity between NameNode and DataNodes is functional. You can use tools like `ping` and `traceroute` to confirm the connectivity.

4. Check the logs of the dead DataNode(s) for any issues. Log location may vary depending on your installation, but you can typically find them in the `/var/log/hadoop-hdfs/` directory. Analyze the logs to identify any errors or issues that may have caused the DataNode to become dead.

    ```
    root@netdata # tail -f /var/log/hadoop-hdfs/hadoop-hdfs-datanode-*.log
    ```

5. If the DataNode service is not running or has crashed, attempt to restart it.

    ```
    root@netdata # systemctl restart hadoop
    ```

### Useful resources

1. [Hadoop Commands Guide](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/CommandsManual.html)

Remember that troubleshooting and resolving issues, especially on a production environment, requires a good understanding of the system and its architecture. Proceed with caution and always ensure data backup and environmental safety before performing any action.