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

Posted to common-dev@hadoop.apache.org by "Amareshwari Sri Ramadasu (JIRA)" <ji...@apache.org> on 2007/10/12 14:56:50 UTC

[jira] Updated: (HADOOP-1898) locking for the ReflectionUtils.logThreadInfo is too conservative

     [ https://issues.apache.org/jira/browse/HADOOP-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sri Ramadasu updated HADOOP-1898:
---------------------------------------------

    Attachment: patch-1898.txt

  I did the changes for locking ReflectionUtils. Here static synchronized method is replaced by a method in a class object. This would not be conservative locking now.

> locking for the ReflectionUtils.logThreadInfo is too conservative
> -----------------------------------------------------------------
>
>                 Key: HADOOP-1898
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1898
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>         Attachments: patch-1898.txt
>
>
> When the RPC servers get into trouble with their call queues backing up, they occasionally dump the call stacks. These are very useful for identifying hot spots, but the locking is too conservative and so all of the handlers are blocked while the thread call stacks are dumped.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.