Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 1 Mar 2013 19:13:13 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12634234.1361909909591.366489.1362165193037@arcas>
In-Reply-To: <JIRA.12634234.1361909909591@arcas>
References: <JIRA.12634234.1361909909591@arcas>
Subject: [jira] [Commented] (HDFS-4532) RPC call queue may fill due to
 current user lookup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590840#comment-13590840 ] 

Suresh Srinivas commented on HDFS-4532:
---------------------------------------

Other than the same concern as Kihwal:
# Minor - indentation in logAuditEvent()
# In a future jira, it would be good to standardize on "method" calls "methodInt". Only "methodInt" performs required locking. Permission checker is initialization, logSync, logging of edits is done in "method". I will follow up on this.

                
> 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