summaryrefslogtreecommitdiffstats
path: root/xlators/cluster/afr/src/afr-transaction.c
diff options
context:
space:
mode:
authorAshish Pandey <aspandey@redhat.com>2018-03-13 14:03:20 +0530
committerAshish Pandey <aspandey@redhat.com>2018-03-14 11:52:05 +0530
commitf32f85c4e6c8128643e1f88fe981a63680e79fe0 (patch)
tree80f4fd9d4f4fdcea1d4f20e93dcf2b267c45110b /xlators/cluster/afr/src/afr-transaction.c
parenta4e34af38d3a58c24862890fe5f4c075d0635e8c (diff)
cluster/ec: Change default read policy to gfid-hash
Problem: Whenever we read data from file over NFS, NFS reads more data then requested and caches it. Based on the stat information it makes sure that the cached/pre-read data is valid or not. Consider 4 + 2 EC volume and all the bricks are on differnt nodes. In EC, with round-robin read policy, reads are sent on different set of data bricks. This way, it balances the read fops to go on all the bricks and avoid heating UP (overloading) same set of bricks. Due to small difference in clock speed, it is possible that we get minor difference for atime, mtime or ctime for different bricks. That might cause a different stat returned to NFS based on which NFS will discard cached/pre-read data which is actually not changed and could be used. Solution: Change read policy for EC as gfid-hash. That will force all the read to go to same set of bricks. Change-Id: I825441cc519e94bf3dc3aa0bd4cb7c6ae6392c84 BUG: 1554743 Signed-off-by: Ashish Pandey <aspandey@redhat.com>
Diffstat (limited to 'xlators/cluster/afr/src/afr-transaction.c')
0 files changed, 0 insertions, 0 deletions