Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-20471

Recheck the design and implementation of FSYNC_WAL durability for WAL

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      This is something derived from discussion in HBASE-19024 around this comment

      We have been supplying user the API to set durability per mutation for a long time, by design the SYNC_WAL durability to call FSDataOutputStream#hflush and FSYNC_WAL FSDataOutputStream#hsync, while in implementation we have been calling hflush for FSYNC_WAL also until HBASE-19024. Although HBASE-19024 tried to fix the syntax with good willing, the implementation there cannot assure the FSYNC_WAL edits are truly hsync'ed due to the disruptor mechanism used in WAL implementation. Here in this JIRA we aim to have more discussion and give it a complete solution.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                carp84 Yu Li
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: