-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.0.0-alpha-1, 2.3.0, 2.2.3, 2.1.9
-
Component/s: wal
-
Labels:None
-
Hadoop Flags:Reviewed
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.
- is broken by
-
HBASE-19024 Configurable default durability for synchronous WAL
-
- Resolved
-
- links to