You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.
The xlator option table can also contain options that load (add to graph) or turn on an xlator. For example, to turn on the barrier xlator, as of today, one has to set option named barrier.barrier to on. This should rather simply be just barrier. IOW, we need a way to identify such options. One approach is to let xlators themselves define which option in option table is a "gobal switch" resulting in the xlator itself being turned on. We can use the newly introduced flags field in the volume_option_t struct.
The text was updated successfully, but these errors were encountered:
prashanthpai
added
GCS/1.0
Issue is blocker for Gluster for Container Storage
and removed
GCS/1.0
Issue is blocker for Gluster for Container Storage
labels
Jul 26, 2018
With the templates support for Volgen(#1229). A Xlator can be enabled by setting [<graph-name>].<option-name>=on in Volinfo. (Volume Set/Reset need to be accommodated once template support merges)
Some Xlators understands enable by having a option in the graph as below,
volume gv7-changelog
type features/changelog
option changelog on
subvolumes gv7-changetimerecorder
end-volume
And some of the Xlators doesn't need any option to say it is enabled. If xlator present in volfile means enabled. This can be handled by setting EnabledByOption field in Volfile template.
With Glusterfs Patch https://review.gluster.org/21813 and Glusterd2 patch #1370 we can enable/disable xlators if option name with same name as xlator exists in respective options table.
The xlator option table can also contain options that load (add to graph) or turn on an xlator. For example, to turn on the barrier xlator, as of today, one has to set option named
barrier.barrier
to on. This should rather simply be justbarrier
. IOW, we need a way to identify such options. One approach is to let xlators themselves define which option in option table is a "gobal switch" resulting in the xlator itself being turned on. We can use the newly introduced flags field in thevolume_option_t
struct.The text was updated successfully, but these errors were encountered: