[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsuyoshi OZAWA updated YARN-1514:
---------------------------------
    Attachment: YARN-1514.7.patch

* Fixing the bug of state management(cleanup works well).
* Removing ZK_TIMEOUT_MS.
* Using ContainerId.newContainerId instead of ContainerId.newInstance.
* Fixing up default values more naturally: ZK_PERF_NUM_APP_DEFAULT is 1000, ZK_PERF_NUM_APPATTEMPT_PER_APP is 10.

About the excessive log messages, it can be suppressed with hadoop --loglevel option:

{code}
$ bin/hadoop --loglevel fatal jar ../../../hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/target/hadoop-yarn-server-resourcemanager-3.0.0-SNAPSHOT-tests.jar TestZKRMStateStorePerf -appSize 5 -appAttemptSize 10 -workingZnode /Test3
ZKRMStateStore takes 39 msec to loadState.
{code}

> Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA
> --------------------------------------------------------------------
>
>                 Key: YARN-1514
>                 URL: https://issues.apache.org/jira/browse/YARN-1514
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Tsuyoshi OZAWA
>            Assignee: Tsuyoshi OZAWA
>             Fix For: 2.7.0
>
>         Attachments: YARN-1514.1.patch, YARN-1514.2.patch, YARN-1514.3.patch, YARN-1514.4.patch, YARN-1514.4.patch, YARN-1514.5.patch, YARN-1514.5.patch, YARN-1514.6.patch, YARN-1514.7.patch, YARN-1514.wip-2.patch, YARN-1514.wip.patch
>
>
> ZKRMStateStore is very sensitive to ZNode-related operations as discussed in YARN-1307, YARN-1378 and so on. Especially, ZKRMStateStore#loadState is called when RM-HA cluster does failover. Therefore, its execution time impacts failover time of RM-HA.
> We need utility to benchmark time execution time of ZKRMStateStore#loadStore as development tool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)