[YARN-7326] Add recursion support and configure RegistryDNS to lookup upstream

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: yarn-native-services
• Target Version/s: yarn-native-services
• Assignee: Eric Yang
• Reporter: Jian He
• Created: 13/Oct/17 17:47
• Updated: 06/Nov/17 22:34
• Resolved: 25/Oct/17 14:39

Description

aw helped to identify these issues:

Now some general bad news, not related to this patch:
Ran a few queries, but this one is a bit concerning:

root@ubuntu:/hadoop/logs# dig @localhost -p 54 .
;; Warning: query response not set

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @localhost -p 54 .
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTAUTH, id: 47794
;; flags: rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; Query time: 0 msec
;; SERVER: 127.0.0.1#54(127.0.0.1)
;; WHEN: Thu Oct 12 16:04:54 PDT 2017
;; MSG SIZE  rcvd: 12

root@ubuntu:/hadoop/logs# dig @localhost -p 54 axfr .
;; Connection to ::1#54(::1) for . failed: connection refused.
;; communications error to 127.0.0.1#54: end of file
root@ubuntu:/hadoop/logs# 

It looks like it effectively fails when asked about a root zone, which is bad.
It's also kind of interesting in what it does and doesn't log. Probably should be configured to rotate logs based on size not date.

The real showstopper though: RegistryDNS basically eats a core. It is running with 100% cpu utilization with and without jsvc. On my laptop, this is triggering my fan.

Issue Links

• relates to: YARN-7384 Remove apiserver cmd and merge service cmd into application cmd