[
https://issues.apache.org/jira/browse/HBASE-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-8680:
---------------------------------
Description:
The JIRA is to check in changes to address performance issues found during my
performance testing as following:
1) When WALEdits belongs to a region which split/merged later, replay incurs
extra waitUntilRegionOnline RPC call
2) Using a single shared connection for replaying achieves better performance.
Everytime creating a new connection, it incurs 4+ seconds to establish a
connection to ZK.
3) other small modifications to mitigate excessive logging
was:
The JIRA is to check in changes to address performance issues found during my
performance testing as following:
1) When WALEdits belongs to a region which split/merged later incur extra
waitUntilRegionOnline RPC call
2) Using a single shared connection for replaying archives better performance.
Everytime creating a new connection, it incurs 4+ seconds to establish a
connection to ZK.
3) other small modifications to mitigate excessive logging
> distributedLogReplay performance regression
> -------------------------------------------
>
> Key: HBASE-8680
> URL: https://issues.apache.org/jira/browse/HBASE-8680
> Project: HBase
> Issue Type: Bug
> Components: MTTR
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Fix For: 0.98.0, 0.95.2
>
> Attachments: 8680-v2.patch, hbase-8680.patch, hbase-8680-v3.patch
>
>
> The JIRA is to check in changes to address performance issues found during my
> performance testing as following:
> 1) When WALEdits belongs to a region which split/merged later, replay incurs
> extra waitUntilRegionOnline RPC call
> 2) Using a single shared connection for replaying achieves better
> performance. Everytime creating a new connection, it incurs 4+ seconds to
> establish a connection to ZK.
> 3) other small modifications to mitigate excessive logging
--
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
