(WIP) [DPE-5303] Update endpoints faster when snap is stopped #610
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
If the snap services are stopped manually by calling
snap stop charmed.postgresql
, the endpoints are not updated in thedatabase
relation endpoint, causing errors in the client charm side.Solution
Improve the Cluster Topology Observer to check other members' REST API when the current member's REST API is not accessible.
This will allow the endpoint to be changed to the IP of the new primary before the
update-status
hook is called the next time.I'm still working on making this more robust.