[
https://issues.apache.org/jira/browse/HADOOP-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915123#comment-13915123
]
Arpit Agarwal commented on HADOOP-10285:
----------------------------------------
Hi Chris, a few questions unrelated to the test failure.
# {{refreshCallQueue}} calls will be accepted by both the datanode and the
client RPC services. Is the former necessary? It looks like DFSAdmin will only
target the client RPC service.
# For the refresh call to work the configuration must have been modified on the
server. Is the administrator required to do so manually before calling refresh?
# Do we need separate protocols for each {{Refresh...}} call? Perhaps we can't
remove existing protocols for backwards compatibility, but going forward can we
have a single protocol? What do you think?
Thanks.
> Admin interface to swap callqueue at runtime
> --------------------------------------------
>
> Key: HADOOP-10285
> URL: https://issues.apache.org/jira/browse/HADOOP-10285
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Chris Li
> Attachments: HADOOP-10285.patch, HADOOP-10285.patch,
> HADOOP-10285.patch, bisection-test.patch, bisection-test.patch,
> bisection-test.patch, bisection-test.patch, bisection-test.patch
>
>
> We wish to swap the active call queue during runtime in order to do
> performance tuning without restarting the namenode.
> This patch adds the ability to refresh the call queue on the namenode,
> through dfsadmin -refreshCallQueue
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
