[
https://issues.apache.org/jira/browse/HBASE-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208782#comment-17208782
]
Duo Zhang commented on HBASE-24813:
-----------------------------------
And it could even consume all the spaces for the data disk...
I've created a jenkins job to execute shell command on jenkins node, and this
is what I found on hbase7...
{noformat}
103G
/home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_HBASE-25152@2/component/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestMasterReplication-output.txt
100G
/home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_HBASE-25152@2/component/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationStatusBothNormalAndRecoveryLagging-output.txt
5.9G
/home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_HBASE-25152@2/component/hbase-server/target/surefire-reports/TEST-org.apache.hadoop.hbase.replication.TestReplicationStatusBothNormalAndRecoveryLagging.xml
5.4G
/home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_HBASE-25152@2/component/hbase-server/target/surefire-reports/TEST-org.apache.hadoop.hbase.replication.TestMasterReplication.xml
{noformat}
https://ci-hadoop.apache.org/job/HBase/job/Test-Docker-Version/36/consoleFull
> 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
>
>
> 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)
