[Gluster-devel] regarding afr changelog options

Vijay Bellur vbellur at redhat.com
Mon Jan 13 08:53:37 UTC 2014


On 01/13/2014 12:25 PM, Pranith Kumar Karampuri wrote:
> Afr depends on the following options to be enabled to work correctly. I am not sure why they are exposed as user configurable options.
> I am thinking of dis-allowing these options from being modified. Please let us know your views.
>
> Option: cluster.entry-change-log
> Description: Entry fops like create/unlink will not perform pre/post fop changelog operations in afr transaction if this option is disabled
> Option: cluster.data-change-log
> Description: Data fops like write/truncate will not perform pre/post fop changelog operations in afr transaction if this option is disabled
> Option: cluster.metadata-change-log
> Description: Metadata fops like setattr/setxattr will not perform pre/post fop changelog operations in afr transaction if this option is disabled
>

Some of these options are useful in testing and troubleshooting. It is 
probably better to mark the type for these options as NO_DOC so that it 
doesn't surface in volume set help.

-Vijay





More information about the Gluster-devel mailing list