summaryrefslogtreecommitdiffstats
path: root/xlators/cluster/afr/src/afr-self-heal-algorithm.h
diff options
context:
space:
mode:
authorPranith Kumar K <pranithk@gluster.com>2012-09-25 10:35:14 +0530
committerAnand Avati <avati@redhat.com>2012-09-25 10:45:08 -0700
commit7add67bcca82e438b4aece5aad096a08a866e26c (patch)
treedc5327b365357a9e4e8bd722f6ffec5757043c0a /xlators/cluster/afr/src/afr-self-heal-algorithm.h
parent5ad96fb5a8c79fe50c21a726a7cbda4eaa3b96cc (diff)
cluster/afr: Wake up post-op on non-co-operative transaction
Problem: The problem is observed when kernel untar is done. One file untar happens every second. The reason for this is, setattr lock is blocked on the prev fd data-transaction full-lock (because of eager-lock). Because of post-op-delay the post-op (xattrop + unlock) of the prev data-transaction happens after 1 sec. Until this the setattr is blocked resulting in performance problems in untar. Fix: Whenever an loc data, meta-data transaction comes, it should wakeup the prev-post-op on the same process' fd. Tests: The performance problem in untar went away. I put a breakpoint in client_finodelk for a 2G file dd and the inodelk is hit only 4 times. This confirms that the change does not affect post-op-delay in a -ve way. Change-Id: Ice3c2a1211f4dca6520a19bc4ba6cb9efb2902ad BUG: 845754 Signed-off-by: Pranith Kumar K <pranithk@gluster.com> Reviewed-on: http://review.gluster.org/3975 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Jeff Darcy <jdarcy@redhat.com> Reviewed-by: Anand Avati <avati@redhat.com>
Diffstat (limited to 'xlators/cluster/afr/src/afr-self-heal-algorithm.h')
0 files changed, 0 insertions, 0 deletions