[
https://issues.apache.org/jira/browse/HDFS-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590915#comment-13590915
]
Daryn Sharp commented on HDFS-4532:
-----------------------------------
@Kihwal:
Good questions, and a cursory scan of the code appears that hftp is not handled
correctly. The servlets attempt to get the rpc proxy from the servlet context,
and if it does it directly invokes methods on the server-side proxy. This
patch doesn't aggravate that issue.
@Suresh:
Oops, will fix the indent. I fully agree on the standardizations, and had
similar thoughts while creating the patch.
> 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
