[CELEBORN-1697] Improve ThreadStackTrace for thread dump #2888
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?
Improve
ThreadStackTracewithsynchronizers,monitors,lockName,lockOwnerName,suspended,inNativefor thread dump.Why are the changes needed?
ThreadStackTrace does not support stack trace including
synchronizers,monitors,lockName,lockOwnerName,suspended,inNativeat present. It's recommend to improveThreadStackTraceof thread dump for more details of thread stack trace.Does this PR introduce any user-facing change?
The response of
ThreadStackin/api/v1/thread_dumpaddssynchronizers,monitors,lockName,lockOwnerName,suspended,inNativefields.Cherry pick:
How was this patch tested?
ApiV1BaseResourceSuite#thread_dump