[
https://issues.apache.org/jira/browse/HBASE-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209071#comment-17209071
]
Hudson commented on HBASE-24813:
--------------------------------
Results for branch branch-2.2
[build #83 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> ReplicationSource should clear buffer usage on ReplicationSourceManager upon
> termination
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-24813
> URL: https://issues.apache.org/jira/browse/HBASE-24813
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 3.0.0-alpha-1, 2.3.1, 2.2.6
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
> Attachments: TestReplicationSyncUpTool.log
>
>
> Following investigations on the issue described by [~elserj] on HBASE-24779,
> we found out that once a peer is removed, thus killing peers related
> *ReplicationSource* instance, it may leave
> *ReplicationSourceManager.totalBufferUsed* inconsistent. This can happen if
> *ReplicationSourceWALReader* had put some entries on its queue to be
> processed by *ReplicationSourceShipper,* but the peer removal killed the
> shipper before it could process the pending entries. When
> *ReplicationSourceWALReader* thread add entries to the queue, it increments
> *ReplicationSourceManager.totalBufferUsed* with the sum of the entries sizes.
> When those entries are read by *ReplicationSourceShipper,*
> *ReplicationSourceManager.totalBufferUsed* is then decreased. We should also
> decrease *ReplicationSourceManager.totalBufferUsed* when *ReplicationSource*
> is terminated, otherwise those unprocessed entries size would be consuming
> *ReplicationSourceManager.totalBufferUsed __*indefinitely, unless the RS gets
> restarted. This may be a problem for deployments with multiple peers, or if
> new peers are added.**
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
