===== git log ====
commit ae7f60235a1a6f9577e0ba2ab1cb425adb9810d0
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Dec 12 21:15:09 2018 -0500

    doc: release notes for release 5.2
    
    Fixes: bz#1649895
    Change-Id: Ic8f59df9d99efafd56c930e30040f046654a1f9e
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit d7a4d256bd86aadcd60668ee37079514dfcf41f3
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Sep 23 16:59:58 2018 +0530

    afr: thin-arbiter 2 domain locking and in-memory state
    
    2 domain locking + xattrop for write-txn failures:
    --------------------------------------------------
    - A post-op wound on TA takes AFR_TA_DOM_NOTIFY range lock and
    AFR_TA_DOM_MODIFY full lock, does xattrop on TA and releases
    AFR_TA_DOM_MODIFY lock and stores in-memory which brick is bad.
    
    - All further write txn failures are handled based on this in-memory
    value without querying the TA.
    
    - When shd heals the files, it does so by requesting full lock on
    AFR_TA_DOM_NOTIFY domain. Client uses this as a cue (via upcall),
    releases AFR_TA_DOM_NOTIFY range lock and invalidates its in-memory
    notion of which brick is bad. The next write txn failure is wound on TA
    to again update the in-memory state.
    
    - Any incomplete write txns before the AFR_TA_DOM_NOTIFY upcall release
    request is got is completed before the lock is released.
    
    - Any write txns got after the release request are maintained in a ta_waitq.
    
    - After the release is complete, the ta_waitq elements are spliced to a
    separate queue which is then processed one by one.
    
    - For fops that come in parallel when the in-memory bad brick is still
    unknown, only one is wound to TA on wire. The other ones are maintained
    in a ta_onwireq which is then processed after we get the response from
    TA.
    
    Change-Id: I32c7b61a61776663601ab0040e2f0767eca1fd64
    updates: bz#1648205
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>


More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v5.2
