You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/08/25 11:14:00 UTC
[jira] [Updated] (HBASE-27321) The ReplicationLogCleaner is not thread safe but can be called from different threads at the same time
[ https://issues.apache.org/jira/browse/HBASE-27321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-27321:
------------------------------
Summary: The ReplicationLogCleaner is not thread safe but can be called from different threads at the same time (was: The ReplicationLogCleaner is not thread safe but can be called from different thread at the same time)
> 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
> Priority: Critical
>
> 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)