Bug 1662122
| Summary: | OpenShift node drop DNS package to dnsmasq caused pod cost 5s to resolve svc hostnames | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | wangzhida <zhiwang> |
| Component: | Networking | Assignee: | Dan Mace <dmace> |
| Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
| Status: | CLOSED DUPLICATE | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aivaraslaimikis, aos-bugs, dmace, hongli, scuppett, sreber, weliang |
| Version: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-18 13:20:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 10
Weibin Liang
2019-01-09 20:52:21 UTC
Get more interesting results when running more testing: Same testing env setup: v3.9.51 Red Hat Enterprise Linux Server release 7.6 (Maipo) openvswitch-2.9.0-83.el7fdp.1.x86_64 openvswitch-selinux-extra-policy-1.0-8.el7fdp.noarch Case1: Cluster created in openstack with instance_type: m1.large Test result: fail Case2: Cluster created in openstack with instance_type: m1.medium Test result: pass Case3: Cluster created in AWS/EC2 with instance_type: m1.large Test result: pass Case4: Cluster created in AWS/EC2 with instance_type: m1.medium Test result: pass All above test results are consistent. (In reply to Weibin Liang from comment #11) Hi, Weibin: Could you help to test to add below settings to centos dc/pod and check whether the latency will be reduced or not ? ... spec template spec ... dnsConfig: options: - name: single-request dnsPolicy: ClusterFirst ... Besides, It is better to test same pods running with hostnetwork because the customer said it has no issue as from nodes. Thanks a lot.
Hi Wangzhida,
Editing dc to have dnsConfig option name:single-request can be a optional workaround for this bug.
Tested in oc v3.11.69
[root@qe-weliang-311master-etcd-nfs-1 ~]# oc edit deploymentconfig.apps.openshift.io/os-sample-python
spec
template
spec
...
dnsConfig:
options:
- name: single-request
dnsPolicy: ClusterFirst
[root@qe-weliang-311master-etcd-nfs-1 ~]# oc rsh os-sample-python-2-jdm45
(app-root) sh-4.2$ OUTPUT=" %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_redirect} %{time_starttransfer} %{time_total}\n"; echo ""; echo " time namelookup connect appconnect pretransfer redirect starttransfer total"; echo "-----------------------------------------------------------------------------------------------------------------"; while true; do echo -n "$(date)"; curl -w "$OUTPUT" -o /dev/null -s $svc5:8080; sleep 2; echo -n "$(date)"; curl -w "$OUTPUT" -o /dev/null -s $svc5:8080; sleep 120; done
time namelookup connect appconnect pretransfer redirect starttransfer total
-----------------------------------------------------------------------------------------------------------------
Tue Jan 15 16:06:29 UTC 2019 0.013 0.013 0.000 0.013 0.000 0.014 0.014
Tue Jan 15 16:06:31 UTC 2019 0.012 0.012 0.000 0.012 0.000 0.014 0.014
Tue Jan 15 16:08:31 UTC 2019 0.012 0.013 0.000 0.013 0.000 0.014 0.014
Tue Jan 15 16:08:33 UTC 2019 0.012 0.012 0.000 0.013 0.000 0.014 0.014
Tue Jan 15 16:10:33 UTC 2019 0.012 0.013 0.000 0.013 0.000 0.014 0.014
Tue Jan 15 16:10:35 UTC 2019 0.012 0.012 0.000 0.013 0.000 0.013 0.013
Tue Jan 15 16:12:35 UTC 2019 0.012 0.013 0.000 0.013 0.000 0.014 0.014
Tue Jan 15 16:12:37 UTC 2019 0.012 0.013 0.000 0.013 0.000 0.013 0.013
*** This bug has been marked as a duplicate of bug 1661928 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |