accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2842) Allow for use of hflush instead of hsync
Date Fri, 23 May 2014 20:09:02 GMT


ASF subversion and git services commented on ACCUMULO-2842:

Commit f654e7faadb9e94e2923087af334a707a4d2c81a in accumulo's branch refs/heads/1.6.1-SNAPSHOT
from [~elserj]
[;h=f654e7f ]

ACCUMULO-2842 Allow configuration of FSDataOutputStream method used to sync WALs.

A critical piece of the bigtable design is using write-ahead logs to ensure
recovery after node failure. The append only file structure is meant to provide
a durable log of events so that the correct state can be reconstructed after
a failure when key-values have not been yet serialized to disk.

Hadoop 2 offers two levels of durability in regards to writes to files in HDFS. HFlush
ensures that all others clients who try to read the file you just wrote data to will
see that new data that was written. HSync will ensure that the data you wrote for that
file is actually sent to the underlying disk. As such, HFlush does not provide durability
when the node crashes without that data being flushed to the drive, while HSync does. HSync
does, however, increase the amount of time needed for sync/flush to complete (as hitting disk
consistently is slower than not).

> Allow for use of hflush instead of hsync
> ----------------------------------------
>                 Key: ACCUMULO-2842
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: logger
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.5.2, 1.6.1, 1.7.0
> We keep getting onto the discussion on hsync versus hflush performance; however, we lack
a way to actually test this.
> Make the invocation of hflush or hsync configurable. It should not change the default,
so users on existing major releases should not be affected unless they choose to change their

This message was sent by Atlassian JIRA

View raw message