[ https://issues.apache.org/jira/browse/HBASE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409199#comment-13409199 ]
Hadoop QA commented on HBASE-6337: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12535622/HBASE-6337v3.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The applied patch generated 5 javac compiler warnings (more than the trunk's current 4 warnings). -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2349//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2349//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2349//console This message is automatically generated. > [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, 0.94.2 > > 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