Closed Bug 1297560 Opened 9 years ago Closed 9 years ago

retry pulse connection establishment

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jonasfj, Unassigned)

References

Details

This took us down because 2 / 3 servers when offline. We can do this at our level, or do it upstream which seems ideal if we can get some buy in, see: https://github.com/squaremo/amqp.node/issues/268
See Also: → 1297547
Solution here is probably just to retry connection establishment, rather than trying to be smart with DNS.
See Also: → 1297759
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
(without looking at the bug) did you confirm that this will cause systems to perform a new DNS lookup on every retry?
nope... and I don't know how we would force a new DNS lookup. I think it depends on the kernel, which probably relies on TTL.
It depends on the resolver lib being used -- the kernel doesn't do DNS. Anyway, that's OK, just something to be aware of. It seems CloudAMQP keeps their TTL low, so this shouldn't be a huge issue: orange-antelope.rmq.cloudamqp.com. 30 IN CNAME ec2-52-53-240-221.us-west-1.compute.amazonaws.com.
Component: Platform Libraries → Services
You need to log in before you can comment on or make changes to this bug.