diff options
| author | Krutika Dhananjay <kdhananj@redhat.com> | 2016-03-29 18:36:08 +0530 |
|---|---|---|
| committer | Jeff Darcy <jdarcy@redhat.com> | 2016-04-11 12:48:53 -0700 |
| commit | c272c71391cea9db817f4e7e38cfc25a7cff8bd5 (patch) | |
| tree | e7f6b47d9cc44fa6fb9812a7738e2a2d2f1cfdce /ChangeLog | |
| parent | d129d4eea33aae5db24dba17adcb04e9d4829817 (diff) | |
features/shard: Make o-direct writes work with sharding
With files opened with o-direct, the expectation is that
the IO performed on the fds is byte aligned wrt the sector size
of the underlying device. With files getting sharded, a single
write from the application could be broken into more than one write
falling on different shards which _might_ cause the original byte alignment
property to be lost. To get around this, shard translator will send fsync
on odirect writes to emulate o-direct-like behavior in the backend.
Change-Id: Ie8a6c004df215df78deff5cf4bcc698b4e17a7ae
BUG: 1322214
Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
Reviewed-on: http://review.gluster.org/13846
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions