HDDS-12585. Ozone Recon - ContainerHealthTask ConstraintViolationException error handling. #8070
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
…ption error handling.
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.
What changes were proposed in this pull request?
This PR change is to handle ContainerHealthTask ConstraintViolationException during the running of ContainerHealthTask.
Currently ContainerHealthTask gets aborted when "pk_container_id" ConstraintViolationException being thrown on UNHEALTHY_CONTAINERS table. Since this is a composite key and task should not be aborted , rather Recon's container health task should update the other fields of table if "pk_container_id" ConstraintViolationException being thrown on UNHEALTHY_CONTAINERS table.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-12585
How was this patch tested?
This patch is tested using existing junit and integration tests and running in local docker cluster.