fix statem data corruption in S5/S8 proxy #335
Merged
Conversation
This file contains 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
The corruption of the statem data only happens when trying to close the context. This was the cause for many of the CI failures in pgw_proxy_SUITE.dns_node_selection. While this might ocure in running instance as well, there should be not operational impact as it only abort a context that is already terminating.
vkatsuba
approved these changes
Mar 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The corruption of the statem data only happens when trying to close
the context. This was the cause for many of the CI failures in
pgw_proxy_SUITE.dns_node_selection.
While this might ocure in running instance as well, there should be
not operational impact as it only abort a context that is already
terminating.