Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TTL control for splitbrain TXT record #61

Closed
ytsarev opened this issue Mar 13, 2020 · 0 comments · Fixed by #64
Closed

TTL control for splitbrain TXT record #61

ytsarev opened this issue Mar 13, 2020 · 0 comments · Fixed by #64
Labels
bug Something isn't working enhancement New feature or request
Milestone
0.6

Comments

@ytsarev
Copy link
Member

ytsarev commented Mar 13, 2020

Currently we are solving potential splitbrain situation of zone delegation configuration by putting timestamp as TXT to heartbeat dns record in edgeDNS zone. Implementation details are in #44

During e2e tests we realized that TTL for this TXT record is implicitly inherited by dns zone configuration of Infoblox.
When TTL is longer then we have an obvious problem with liveness check incorrectness.
We need to find a reliable way to control TTL of edgeDNS splitbrain TXT records.

Current hypo is to use special API call of TTL update
image

It will also require another upstream modification of https://github.com/infobloxopen/infoblox-go-client as it does not support TTL handling.

Issue is still workaroundable by setting low TTL in edgeDNSzone configuration in Infoblox
@ytsarev ytsarev added bug Something isn't working enhancement New feature or request labels Mar 13, 2020
@ytsarev ytsarev added this to the 0.6 milestone Mar 13, 2020
@ytsarev ytsarev mentioned this issue Mar 14, 2020
Open
ytsarev added a commit that referenced this issue Mar 16, 2020
@ytsarev
Set low TTL on split brain TXT record via infoblox API
c36c12c 
* Fixes #61 by setting low 30 sec TTL so split brain
  timestamp will never be artificially stale
* Based on ABSA enhancement of infoblox-go-client
* Related PR upstream: infobloxopen/infoblox-go-client#89
@ytsarev ytsarev mentioned this issue Mar 16, 2020
Merged
ytsarev added a commit that referenced this issue Mar 16, 2020
@ytsarev
Set low TTL on split brain TXT record via infoblox API (#64)
b2d3add 
* Fixes #61 by setting low 30 sec TTL so split brain
  timestamp will never be artificially stale
* Based on ABSA enhancement of infoblox-go-client
* Related PR upstream: infobloxopen/infoblox-go-client#89
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
0.6
Development

Successfully merging a pull request may close this issue.

Set low TTL on split brain TXT record via infoblox API k8gb-io/k8gb
1 participant
@ytsarev