You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2017/10/24 21:54:00 UTC
[jira] [Comment Edited] (YARN-7326) Add recursion support and
configure RegistryDNS to lookup upstream
[ https://issues.apache.org/jira/browse/YARN-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217758#comment-16217758 ]
Eric Yang edited comment on YARN-7326 at 10/24/17 9:53 PM:
-----------------------------------------------------------
Fix white space issues. It looks like the filter mechanism is causing unit tests to fail on Jenkins. It is possible Jenkin's only DNS server is 127.0.0.1, (the default on ubuntu). By filtering out the local dns servers, it fails. Hence, the filter mechanism should only apply to running registryDNS on port 53.
was (Author: eyang):
Fix white space issues, the test failure isn't related to this patch.
> Add recursion support and configure RegistryDNS to lookup upstream
> ------------------------------------------------------------------
>
> Key: YARN-7326
> URL: https://issues.apache.org/jira/browse/YARN-7326
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jian He
> Assignee: Eric Yang
> Attachments: YARN-7326.yarn-native-services.001.patch, YARN-7326.yarn-native-services.002.patch, YARN-7326.yarn-native-services.003.patch, YARN-7326.yarn-native-services.004.patch, YARN-7326.yarn-native-services.005.patch, YARN-7326.yarn-native-services.006.patch, YARN-7326.yarn-native-services.007.patch
>
>
> [~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:
> {code}
> 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#
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org