summaryrefslogtreecommitdiffstats
path: root/playbooks/byo/openshift-glusterfs
diff options
context:
space:
mode:
authorSteve Kuznetsov <skuznets@redhat.com>2017-06-13 09:57:00 -0700
committerSteve Kuznetsov <skuznets@redhat.com>2017-06-13 09:57:00 -0700
commitd04cf6b2ae12596a481c37b8d25f652f099ae5cd (patch)
tree433afb3da0ab8aff0ee9a988442576c3af61bd6c /playbooks/byo/openshift-glusterfs
parentc31b418922ec5771888c22cd2d608596402c8a7e (diff)
downloadopenshift-d04cf6b2ae12596a481c37b8d25f652f099ae5cd.tar.gz
openshift-d04cf6b2ae12596a481c37b8d25f652f099ae5cd.tar.bz2
openshift-d04cf6b2ae12596a481c37b8d25f652f099ae5cd.tar.xz
openshift-d04cf6b2ae12596a481c37b8d25f652f099ae5cd.zip
Disable negative caching, set cache TTL to 1s
When running headless services as pods on OpenShift, no ClusterIP is assigned. In these cases, peer pods are relying on DNS to locate the service endpoints. When a pod is deleted or another trigger causes the endpoint to change, the OpenShift DNS is updated immediately. However, dnsmasq has a default TTL of 30s, so the wrong response is returned on name resolution. Removing negative caching and turning the TTL to a very short 1s should resolve the issue. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Diffstat (limited to 'playbooks/byo/openshift-glusterfs')
0 files changed, 0 insertions, 0 deletions