+1 from Geo-rep.
In Geo-rep, Meta Volume is optional setting to increase the stability of
Geo-replication. If meta volume is configured, geo-rep saves lock files
for each subvolume to decide Active/Passive geo-rep worker. If not
configured it fallback to old method of deciding Active/Passive based on
node-uuid.
3 way replicated meta volume is good for consistency.
I think once Glusterd implements distributed store, we can migrate from
metavol to distributed store. :)
--
regards
Aravinda
On 04/07/2015 03:56 PM, Rajesh Joseph wrote:
Hi all,
In gluster 3.7 multiple features (Snapshot scheduler, NFS Ganesha, Geo-rep) are planning to use
additional volume to store metadata related to these features. This volume needs to be manually
created and explicitly managed by an admin.
I think creating and managing these many metadata volume would be an overhead for an admin. Instead
of that I am proposing to have a single unified metata-volume which can be used by all these features.
For simplicity and easier management we are proposing to have a pre-defined volume name.
If needed this name can be configured using a global gluster option.
Please let me know if you have any suggestions or comments.
Thanks & Regards,
Rajesh
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
