[jira] [Updated] (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:all-tabpanel ] Masatake Iwasaki updated HADOOP-17446: -- Target Version/s: 3.4.0, 3.3.9, 3.2.5 (was: 3.4.0, 3.2.4, 3.3.9) > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] Chao Sun updated HADOOP-17446: -- Target Version/s: 3.4.0, 3.2.4, 3.3.3 (was: 3.4.0, 3.3.2, 3.2.4) > 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.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] Xiaoqiao He updated HADOOP-17446: - Target Version/s: 3.4.0, 3.3.2, 3.2.4 (was: 3.4.0, 3.2.3, 3.3.2) ===Bulk update=== planning to cut the branch for Hadoop 3.2.3 release, and this jira targets 3.2.3 currently. Bulk update the targets to 3.2.4. Please feel free to change back if you think it can be finished in the next few weeks. Thanks. > 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.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] Wei-Chiu Chuang updated HADOOP-17446: - Target Version/s: 3.4.0, 3.2.3, 3.3.2 (was: 3.3.1, 3.4.0, 3.2.3) > 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.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] Wei-Chiu Chuang updated HADOOP-17446: - Target Version/s: 3.3.1, 3.4.0, 3.2.3 (was: 3.3.0, 3.4.0, 3.2.3) > 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.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] ASF GitHub Bot updated HADOOP-17446: Labels: pull-request-available (was: ) > 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: 10m > 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.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
