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 2019/12/30 02:30:00 UTC

[jira] [Assigned] (HBASE-23587) The FSYNC_WAL flag does not work on branch-2.x

     [ https://issues.apache.org/jira/browse/HBASE-23587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang reassigned HBASE-23587:
---------------------------------

    Assignee: Duo Zhang

> The FSYNC_WAL flag does not work on branch-2.x
> ----------------------------------------------
>
>                 Key: HBASE-23587
>                 URL: https://issues.apache.org/jira/browse/HBASE-23587
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.1.9, 2.2.4
>
>
> You can check the reference to SyncFuture.isForceSync, no one calls it. And in FSHLog, we always use the field useHsync instead of getting one from the SyncFuture. I think the problem here is that we have done some optimization for batching the sync futures on branch-2.x so it is not easy to get the forceSync flag from a single SyncFuture when doing sync.
> But anyway, we need to fix this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)