hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sri Ramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1898) locking for the ReflectionUtils.logThreadInfo is too conservative
Date Tue, 16 Oct 2007 08:28:50 GMT

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

Amareshwari Sri Ramadasu updated HADOOP-1898:

    Status: Patch Available  (was: Open)

Instead of previous patch changes of introducing a new class, now we do it by introducing
a synchronized block in the method. 
Any comments on the patch?

> 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, patch-1898.txt, 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.

View raw message