[
https://issues.apache.org/jira/browse/HDFS-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590174#comment-13590174
]
Hadoop QA commented on HDFS-4532:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12571507/HDFS-4532.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4018//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4018//console
This message is automatically generated.
> RPC call queue may fill due to current user lookup
> --------------------------------------------------
>
> Key: HDFS-4532
> URL: https://issues.apache.org/jira/browse/HDFS-4532
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HDFS-4532.branch-23.patch, HDFS-4532.patch
>
>
> Audit logging need to invoke {{UGI.getCurrentUser}} to log the user
> performing an operation. This is a synch'ed method, so audit logging is
> effectively serializing the completion of concurrent read ops. Under very
> heavy load, RPC throughput drops dramatically, the call queue fills with
> thousands of waiting operations, and clients begin timing out. Jstack shows
> all but one call handler blocked on {{UGI.getCurrentUser}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
