-
Notifications
You must be signed in to change notification settings - Fork 27
[DPE-3349] Handle S3 relation in primary non-leader unit #375
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.
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
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
f698f92
Handle S3 relation in primary non-leader unit
marceloneppel 9fe08d3
Fix relation data removal
marceloneppel ddef181
Update integration test
marceloneppel 8920688
Fix existing unit tests
marceloneppel cf78547
Add extra unit tests
marceloneppel 3ec248b
Add unit test for peer relation changed event handler
marceloneppel 553489e
Merge remote-tracking branch 'origin/main' into dpe-3349-initialise-s…
marceloneppel 1064d94
Handle pgBackRest service check when the primary was not elected yet
marceloneppel e24d703
Speedup the new check on test
marceloneppel 2e55c4d
Add log call
marceloneppel 450f78e
Merge remote-tracking branch 'origin/main' into dpe-3349-initialise-s…
marceloneppel ec069dd
Speed up events
marceloneppel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have to check the unit databags anyway, would it make sense to not set the app data at all? that way we should be able to have a single flow using the unit data, instead of having to check two places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Let me try to recall if there is any reason for this approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remembered the reason I have chosen the approach with both application and unit relation databags: using only the unit relation databag, if we scale down the application and the primary unit is removed, we need to handle the transfer of the stanza name to one of the remaining units in something like the relation departed event or keep the stanza name in all the units, which seems not so good as keeping it in the application relation databag.