[
https://issues.apache.org/jira/browse/HADOOP-17268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198764#comment-17198764
]
Ayush Saxena commented on HADOOP-17268:
---------------------------------------
I couldn't check the patch, but what is the use case for this.
The Namenode is suppose to respond to the client, if it is busy, it should
reply with a delay, what if it responds with {{TOO_BUSY}}, Anyway the client
will retry on it again, for obvious reasons.
Is it something related to {{Observers}}?
> Add RPC Quota to NameNode.
> --------------------------
>
> Key: HADOOP-17268
> URL: https://issues.apache.org/jira/browse/HADOOP-17268
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Attachments: HADOOP-17268.001.patch
>
>
> Add the ability of rpc request quota to NameNode. All the requests exceeding
> quota would end with a 'Server too busy' exception. This can prevent users
> from overusing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
