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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2007/10/16 18:13:50 UTC
[jira] Commented: (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:comment-tabpanel#action_12535281 ]
Hadoop QA commented on HADOOP-1898:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12367802/patch-1898.txt
against trunk revision r584939.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/956/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/956/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/956/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/956/console
This message is automatically generated.
> 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.