@son210802
Quick postmortem: looks like this was an outbound DNS query cache miss to our service provider discovery service. We read through to the backup service provider catalog cluster, but high latency to our Australian datacenter meant the request timed out and landed in the service provider catalog cluster request retry queue. Once this was processed we were able to resolve the current PfpHaloMutexService leader and request a write lock. Worked fine from there.
1 reply
0 recast
3 reactions