You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "wenfeiyi666 (Jira)" <ji...@apache.org> on 2020/07/15 01:47:00 UTC

[jira] [Assigned] (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:all-tabpanel ]

wenfeiyi666 reassigned HBASE-24737:
-----------------------------------

    Assignee: wenfeiyi666

> 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: wenfeiyi666
>            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)