IBM Support

Hadoop NameNode becomes un-responsive due to Trash configuration

Troubleshooting


Problem

Although the NameNode service may become busy due to several activities, certain Trash configurations can result in a huge volume of deleted files being "expunged" at a single point in time.

Symptom

During normal operation using IBM BigInsights, the Hadoop NameNode service may become unresponsive preventing job execution; in a High Availability environment using Zookeeper, this may result in Zookeeper considering the NameNode service is unavailable and instigate failover, which may be repeated several times.

[{"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Server","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.1.2;3.0.0.2;4.0.0;4.1.0","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
08 April 2021

UID

swg21966396