[
https://issues.apache.org/jira/browse/HBASE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409182#comment-13409182
]
chunhui shen commented on HBASE-6337:
-------------------------------------
bq.If you can put the 0.94 patch onto a real cluster and collect performance
numbers, that would be great.
If the distributed-log-splitting's bottleneck is not on the SplitLogManager,
this improvement is just reducing NN operations, else it will decrease the time
of distributed-log-splitting.
We have test for the case:
9 regionserver, 2500 regions per hlog file, total 280 hlog files,16 ms per
rename operation
With the patch, reduce the time of distributed-log-splitting from 3+ hours to
20+ mins
> [MTTR] Remove renaming tmp log file in SplitLogManager
> -------------------------------------------------------
>
> Key: HBASE-6337
> URL: https://issues.apache.org/jira/browse/HBASE-6337
> Project: HBase
> Issue Type: Bug
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.96.0
>
> Attachments: HBASE-6337v1.patch, HBASE-6337v2.patch,
> HBASE-6337v3.patch
>
>
> As HBASE-6309 mentioned, we also encounter problem of
> distributed-log-splitting take much more time than matser-local-log-splitting
> because lots of SplitLogManager 's renaming operations when finishing task.
> Could we try to remove renaming tmp log file in SplitLogManager through
> splitting log to regions' recover.edits directory directly as the same as the
> master-local-log-splitting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
