[Bugs] [Bug 1333358] New: Provide way to determine if xlator option 'resync-failed-syncs-after-fsync' is supported

[bugzilla at redhat.com]

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

            Bug ID: 1333358
           Summary: Provide way to determine if xlator option
                    'resync-failed-syncs-after-fsync' is supported
           Product: GlusterFS
           Version: mainline
         Component: libgfapi
          Keywords: FutureFeature, Triaged
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
        QA Contact: sdharane at redhat.com
                CC: bugs at gluster.org, jcody at redhat.com, rjoseph at redhat.com
            Blocks: 1333142



In the current upstream Gluster, the write-behind cache supports a xlator
option 'resync-failed-syncs-after-fsync', which has Gluster retain the cache on
fsync failure, until the file descriptor is flushed/closed.  With this QEMU,
when using the libglusterfs library, can perform retries on a fsync failure.

However, QEMU has no way of determining at runtime if this xlator option is
supported.  The api glfs_set_xlator_option() will return success even for
unknown options.  It would be very useful for us to be able to determine if we
can use the new xlator option - until we can determine if it is support, QEMU
must act as if it is not supported.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1333142
[Bug 1333142] Provide way to determine if xlator option
'resync-failed-syncs-after-fsync' is supported
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.