[
https://issues.apache.org/jira/browse/HBASE-23587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007816#comment-17007816
]
Hudson commented on HBASE-23587:
--------------------------------
Results for branch branch-2.2
[build #743 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/743/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/743//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/743//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/743//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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.2.3, 2.1.9
>
>
> 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)
