Shulou(Shulou.com)06/03 Report--

Question:

WARN org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Waited 19016 ms (timeout=20000 ms) for a response for sendEdits. Succeeded so far: [10.80.248.17:8486]

Namenode gc overhead limit exceeded

Reason:

1. Network reason-check is normal. If there is a delay, you can set hdfs-site.xml dfs.qjournal.write-txns.timeout.ms=60000.

2 for the reasons of JVM GC, it is possible that the cluster has been running for a long time, and the growth of metadata information leads to exceeding the memory configuration. Generally, JVMs have memory limits.

Find that the default namenode memory size is 1000m

Modify: hadoop-env.sh

Export HADOOP_HEAPSIZE=20

Start namenode for normal use.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.