summaryrefslogtreecommitdiffstats
path: root/tests/00-geo-rep
diff options
context:
space:
mode:
authorAshish Pandey <aspandey@redhat.com>2018-11-28 11:22:52 +0530
committerXavi Hernandez <xhernandez@redhat.com>2019-03-27 11:14:48 +0000
commit313dcefe7a62bd16cd794040df068f9bec9c6927 (patch)
treecad3c2fab04b8f54be0b5c0b2450c5af8019e10d /tests/00-geo-rep
parent8016d51a3bbd410b0b927ed66be50a09574b7982 (diff)
cluster/ec: Don't enqueue an entry if it is already healing
Problem: 1 - heal-wait-qlength is by default 128. If shd is disabled and we need to heal files, client side heal is needed. If we access these files that will trigger the heal. However, it has been observed that a file will be enqueued multiple times in the heal wait queue, which in turn causes queue to be filled and prevent other files to be enqueued. 2 - While a file is going through healing and a write fop from mount comes on that file, it sends write on all the bricks including healing one. At the end it updates version and size on all the bricks. However, it does not unset dirty flag on all the bricks, even if this write fop was successful on all the bricks. After healing completion this dirty flag remain set and never gets cleaned up if SHD is disabled. Solution: 1 - If an entry is already in queue or going through heal process, don't enqueue next client side request to heal the same file. 2 - Unset dirty on all the bricks at the end if fop has succeeded on all the bricks even if some of the bricks are going through heal. Change-Id: Ia61ffe230c6502ce6cb934425d55e2f40dd1a727 updates: bz#1593224 Signed-off-by: Ashish Pandey <aspandey@redhat.com>
Diffstat (limited to 'tests/00-geo-rep')
0 files changed, 0 insertions, 0 deletions