diff options
author | Ravishankar N <ravishankar@redhat.com> | 2015-08-04 18:37:47 +0530 |
---|---|---|
committer | Kaushal M <kaushal@redhat.com> | 2015-08-31 08:03:09 -0700 |
commit | 7924eb1a11fe0b1443903a69b7e93e4767061064 (patch) | |
tree | cba81e366f8bdab5a2c726c32aee0a6025c7a4cc /xlators/features | |
parent | 1cc232c9bfad531ec2ee9052fa198519353516a1 (diff) |
afr: modify afr_txn_nothing_failed()
Backport of http://review.gluster.org/#/c/11827/
In an AFR transaction, we need to consider something as failed only if the
failure (either in the pre-op or the FOP phase) occurs on the bricks on which a
transaction lock was obtained.
Without this, we would end up considering the transaction as failure even on the
bricks on which the lock was not obtained, resulting in unnecessary fsyncs
during the post-op phase of every write transaction for non-appending writes.
Change-Id: Iee79e5d85dc7b4c41459d8bdd04a8454bdaf9a9d
BUG: 1255698
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
Reviewed-on: http://review.gluster.org/11985
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Diffstat (limited to 'xlators/features')
0 files changed, 0 insertions, 0 deletions