[Bugs] [Bug 1549606] Eager lock should be present for both metadata and data transactions

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1549606



--- Comment #1 from Pranith Kumar K <pkarampu at redhat.com> ---
    cluster/afr: Make AFR eager-locking similar to EC

    Problem:
    1) Afr's eager-lock only works for data transactions.
    2) When there are conflicting writes, write with conflicting region
initiates
    unlock of eager-lock leading to extra pre-ops and post-ops on the file.
When
    eager-lock goes off, it leads to extra fsyncs for random-write workload in
afr.

    Solution (that is modeled after EC):
    In EC, when there is a conflicting write, it waits for the current write to
    complete before it winds the conflicted write. This leads to better
utilization
    of network and disk, because we will not be doing extra xattrops and FSYNCs
and
    inodelk/unlock.

    I tried to model the solution based on EC's locking, but it is not similar
to
    AFR because we had to keep backward compatibility.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.