[Bugs] [Bug 1356079] New: Introduce common transaction framework as an alternative to lock-acquisition by individual translators on client stack

[bugzilla at redhat.com]

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

            Bug ID: 1356079
           Summary: Introduce common transaction framework as an
                    alternative to lock-acquisition by individual
                    translators on client stack
           Product: GlusterFS
           Version: mainline
         Component: core
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
                CC: bugs at gluster.org



Description of problem:

Original inventor of the idea - Xavier Hernandez <xhernandez at datalab.es>

The basic idea is to introduce the notion of transactions into libglusterfs for
fops that need to be executed on multiple bricks atomically.
This way xlators needing transactions will use a common API. Whether the API
uses locks or other mechanisms as a means to ensure atomicity is
implementation-dependent and abstracted out. This makes the cluster translators
light-weight, and reduces code duplication. It also makes it easy to implement
newer translators that might need transactional semantics in some of their
fops. This could also enable multiple transactions of a single fop (one txn
from AFR and one from DHT, for example) to be serviced by a single lock. Some
of the consumers of this framework could be AFR, DHT, EC and sharding.

The details are still being worked out. Will post the design once it is ready
here and on mailing lists.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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