-
Notifications
You must be signed in to change notification settings - Fork 351
Closed
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: docsImprovement to the documentation for an API.Improvement to the documentation for an API.
Description
Question
We are configuring HA databases and the idea is that when one of them is down, the other should still be accessible -- bc HA, of course. Will readiness still report as operable if one of the replicas configured is down? What will happen in the event all are down? Will readiness still report OK?
The doc is mum on this which is why we pursued this, as we'd observed behavior that suggested when one was down readiness was no longer OK and the pods were pulled from their k8s Services. But looking at the code once more, this may have been isolated to cloud sql v1 as I'm not seeing how that would manifest here unless stopped or started were somehow tripping the failure.
From #2419
Code
Additional Details
No response
enocom
Metadata
Metadata
Assignees
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: docsImprovement to the documentation for an API.Improvement to the documentation for an API.