[ https://issues.apache.org/jira/browse/HBASE-14953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053515#comment-15053515 ]
Hadoop QA commented on HBASE-14953: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12776889/HBASE-14953-V2.patch against master branch at commit 22b95aebcd7fc742412ab514520008fda5e327de. ATTACHMENT ID: 12776889 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0 2.7.1) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 checkstyle{color}. The applied patch does not generate new checkstyle errors. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn post-site goal succeeds with this patch. {color:green}+1 core tests{color}. The patch passed unit tests in . {color:green}+1 zombies{color}. No zombie tests found running at the end of the build. Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/16835//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/16835//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/16835//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/16835//console This message is automatically generated. > HBaseInterClusterReplicationEndpoint: Do not retry the whole batch of edits > in case of RejectedExecutionException > ----------------------------------------------------------------------------------------------------------------- > > Key: HBASE-14953 > URL: https://issues.apache.org/jira/browse/HBASE-14953 > Project: HBase > Issue Type: Bug > Components: Replication > Affects Versions: 2.0.0, 1.2.0, 1.3.0 > Reporter: Ashu Pachauri > Assignee: Ashu Pachauri > Priority: Critical > Attachments: HBASE-14953-V1.patch, HBASE-14953-V2.patch > > > When we have wal provider set to multiwal, the ReplicationSource has multiple > worker threads submitting batches to HBaseInterClusterReplicationEndpoint. In > such a scenario, it is quite common to encounter RejectedExecutionException > because it takes quite long for shipping edits to peer cluster compared to > reading edits from source and submitting more batches to the endpoint. > The logs are just filled with warnings due to this very exception. > Since we subdivide batches before actually shipping them, we don't need to > fail and resend the whole batch if one of the sub-batches fails with > RejectedExecutionException. Rather, we should just retry the failed > sub-batches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)