You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sun Xin (Jira)" <ji...@apache.org> on 2021/04/27 03:17:00 UTC
[jira] [Commented] (HBASE-24737) Find a way to resolve
WALFileLengthProvider#getLogFileSizeIfBeingWritten problem
[ https://issues.apache.org/jira/browse/HBASE-24737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332899#comment-17332899 ]
Sun Xin commented on HBASE-24737:
---------------------------------
Thank [~zhangduo] for reviewing.
Failed UTs are not related, I will fix these UTs in HBASE-25110.
> Find a way to resolve WALFileLengthProvider#getLogFileSizeIfBeingWritten problem
> --------------------------------------------------------------------------------
>
> Key: HBASE-24737
> URL: https://issues.apache.org/jira/browse/HBASE-24737
> Project: HBase
> Issue Type: Sub-task
> Reporter: Guanghao Zhang
> Assignee: Sun Xin
> Priority: Major
>
> Now we use WALFileLengthProvider#getLogFileSizeIfBeingWritten to get the synced wal length and prevent replicating unacked log entries. But after offload ReplicationSource to new ReplicationServer, we need a new way to resolve this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)