[HBASE-7801] Allow a deferred sync option per Mutation.

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.94.6, 0.95.0
• Fix Version/s: 0.98.0, 0.94.7, 0.95.1

Release Note

HBase clients from 0.94.7 going forward support the following new API for Mutations (Put/Delete/Append/Increment).
Mutation.setDurability(Durability). Possible durability settings are: USE_DEFAULT (use whatever the table has been configured with), SKIP_WAL (do not write anything to the WAL), ASYNC_WAL (write to the WAL asynchronously), SYNC (write to the WAL synchrously), FSYNC (write to the WAL synchronously and force to disc everywhere - currently not supported).

Regionservers prior to 0.94.7 with ignore anything but SKIP_WAL and assume USE_DEFAULT.

• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 09/Feb/13 06:46
• Updated: 27/Sep/19 10:23
• Resolved: 15/Apr/13 18:46

Description

Won't have time for parent. But a deferred sync option on a per operation basis comes up quite frequently.
In 0.96 this can be handled cleanly via protobufs and 0.94 we can have a special mutation attribute.

For batch operation we'd take the safest sync option of any of the mutations. I.e. if there is at least one that wants to be flushed we'd sync the batch, if there's none of those but at least one that wants deferred flush we defer flush the batch, etc.

Issue Links

• is depended upon by: HBASE-8848 Add durability options for mutations to Thrift
• relates to: HBASE-7855 Allow grouping edits for different regions (on the same server) and write them into a single WALEdit
• relates to: HBASE-9093 Hbase client API: Restore the writeToWal method