[YARN-8216] Reduce RegistryDNS port ping logging

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.1.0
• Target Version/s: 3.2.0, 3.1.1
• Assignee: Unassigned
• Reporter: Eric Yang
• Created: 26/Apr/18 17:11
• Updated: 27/Apr/18 01:24
• Resolved: 27/Apr/18 01:24

Description

System monitoring software usually send a tcp packet to test if port is alive. This can cause RegistryDNS to throw BufferUnderflowException.

2018-04-26 17:07:55,846 WARN org.apache.hadoop.util.concurrent.ExecutorHelper: Execution exception when running task in RegistryDNS 3
2018-04-26 17:07:55,847 WARN org.apache.hadoop.util.concurrent.ExecutorHelper: Caught exception in thread RegistryDNS 3:
java.nio.BufferUnderflowException
        at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
        at org.apache.hadoop.registry.server.dns.RegistryDNS.nioTCPClient(RegistryDNS.java:771)
        at org.apache.hadoop.registry.server.dns.RegistryDNS$3.call(RegistryDNS.java:846)
        at org.apache.hadoop.registry.server.dns.RegistryDNS$3.call(RegistryDNS.java:843)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

This is perfectly normal, but it would be nice to hide this error message to reduce verbose logging on port ping.

Issue Links

• is duplicated by: YARN-8211 Yarn registry dns log finds BufferUnderflowException on port ping