You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Masatake Iwasaki (Jira)" <ji...@apache.org> on 2022/07/12 16:12:00 UTC

[jira] [Commented] (HADOOP-17446) Print the thread parker and lock information in stacks page

    [ https://issues.apache.org/jira/browse/HADOOP-17446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565910#comment-17565910 ] 

Masatake Iwasaki commented on HADOOP-17446:
-------------------------------------------

update the targets to 3.2.5 for preparing 3.2.4 release.

> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org