[
https://issues.apache.org/jira/browse/HADOOP-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Li updated HADOOP-10285:
------------------------------
Attachment: HADOOP-10285.patch
Okay, here's 10285, adding the comment
On closer inspection, a true end to end test would be difficult, because
refreshCallQueue() has a void response, so we'd have to go digging around in
the server's internals to verify (we'd have to add more @visibleForTesting
getters)
We can open another issue to refactor the refresh*protos into one generic
RefreshConfigurationProto, which can provide a return value indicating success
or failure. This will also make testing easier to do.
Let me know if that's okay.
> 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, 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)
