HDDS-6257. Wrong stack trace for S3 errors #3066
Merged
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?
S3 Gateway logs exception in
S3ErrorTable.newError, but the stack trace is wrong.Note that both errors have the same stack trace. It always points to the operation that first accessed
S3ErrorTableclass (i.e. the one that triggered the first error, in this case ahead-bucketoperation).This change fixes the stack trace by passing the original exception, if available, to the method which logs, instead of using the predefined
OS3Exception's stack trace.https://issues.apache.org/jira/browse/HDDS-6257
How was this patch tested?
Set log level to debug:
Tested with the following commands. Verified that stack traces are unique.
CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/1818745426