[ 
https://issues.apache.org/jira/browse/HBASE-27321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17596913#comment-17596913
 ] 

Hudson commented on HBASE-27321:
--------------------------------

Results for branch master
        [build #668 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/668/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/668/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/668/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/668/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> The ReplicationLogCleaner is not thread safe but can be called from different 
> threads at the same time
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-27321
>                 URL: https://issues.apache.org/jira/browse/HBASE-27321
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Replication
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> In preClean method we will update the class fields and then use them in the 
> getDeletableFiles method. This implies that we will have only one cleaner run 
> at the same time.
> But actually, in MasterRpcServices.runCleanerChore, we will call execute the 
> HFileCleaner and LogCleaner directly, not in the cleanerChore thread.
> This could cause data loss for replication, which is a very serious problem.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to