[
https://issues.apache.org/jira/browse/HADOOP-17446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043292#comment-18043292
]
ASF GitHub Bot commented on HADOOP-17446:
-----------------------------------------
github-actions[bot] commented on PR #2574:
URL: https://github.com/apache/hadoop/pull/2574#issuecomment-3621410996
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Print the thread parker and lock information in stacks page
> -----------------------------------------------------------
>
> Key: HADOOP-17446
> URL: https://issues.apache.org/jira/browse/HADOOP-17446
> Project: Hadoop Common
> Issue Type: New Feature
> Components: common
> Affects Versions: 3.4.0
> Reporter: Baolong Mao
> Assignee: Baolong Mao
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2020-12-25-08-32-32-982.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Sometimes, our service stuck because of some lock held by other thread, but
> we can get nothing from "stacks" for ReadWriteLock, and it is widely used in
> our services, like the fslock, cplock, dirlock of namenode.
> Luckily, we can get thread parker from Thread object, it can help us see the
> thread parker clearly.
> !image-2020-12-25-08-32-32-982.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
