diff options
author | Krutika Dhananjay <kdhananj@redhat.com> | 2015-01-16 14:26:45 +0530 |
---|---|---|
committer | Niels de Vos <ndevos@redhat.com> | 2015-02-05 07:04:47 -0800 |
commit | 4b3981d2c9b4cafa24398765b3d0c8a4d45d43b1 (patch) | |
tree | cd00721b993e5689f7e68315c9d5a478be6ac668 /xlators/features | |
parent | bb2df4e63fa8a5d65f18b4a5efc757e8d475fbff (diff) |
cluster/dht: Fix incorrect updates to parent times
Backport of: http://review.gluster.org/9457
In directory write FOPs, as far as updates to timestamps associated
with parent by DHT is concerned, there are three possibilities:
a) time (in sec) gotten from child of DHT < time (in sec) in inode ctx
b) time (in sec) gotten from child of DHT = time (in sec) in inode ctx
c) time (in sec) gotten from child of DHT > time (in sec) in inode ctx
In case (c), for time in nsecs, it is the value returned by DHT's child
that must be selected. But what DHT_UPDATE_TIME ends up doing is to choose
the maximum of (time in nsec gotten from DHT's child, time in nsec in inode ctx).
Change-Id: I1388e374c8a2029f3b8919380e68620e7591bde6
BUG: 1186121
Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
Reviewed-on: http://review.gluster.org/9496
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
Diffstat (limited to 'xlators/features')
0 files changed, 0 insertions, 0 deletions