[Gluster-users] Distributed Replicated Volumes and 'same server redundancy'

Craig Carl craig at gluster.com
Fri Dec 3 06:14:45 UTC 2010


Stephan -
    Bricks are mirrored in the order they are listed on the create 
volume command, so as long as you type the command properly you will be 
able to mirror across nodes. We call this "rack-awareness". There is an 
example here - 
http://gluster.org/pipermail/gluster-users/2010-December/006001.html

Please let me know if you have any other questions.

Thanks,

Craig

-->
Craig Carl
Senior Systems Engineer; Gluster, Inc.
Cell - (408) 829-9953 (California, USA)
Office - (408) 770-1884
Gtalk - craig.carl at gmail.com
Twitter - @gluster
http://rackerhacker.com/2010/08/11/one-month-with-glusterfs-in-production/



On 11/30/2010 11:17 PM, Raghavendra G wrote:
> Hi Stefan,
>
> Can you use gluster cli to create replicated distribute setup? instructions on how to use gluster cli can be found in gluster documentation
> http://www.gluster.com/community/documentation/index.php/Main_Page
>
> regards,
> Raghavendra.
>
> ----- Original Message -----
> From: "Stefan de Konink"<stefan at konink.de>
> To: gluster-users at gluster.org
> Sent: Saturday, November 27, 2010 4:49:45 PM
> Subject: [Gluster-users] Distributed Replicated Volumes and 'same server	redundancy'
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hello,
>
>
> Currently I have multiple servers having 12 SATA disks each. Access to
> the individual disks is faster than one big volume in RAID5. Given that
> the potential failure and recovery time for RAID0 from the network is
> big, I decided distributed replicated volumes might be more interesting.
>
> If I create a Trusted Storage Pool consisting of the servers exporting
> each different disk as new brick and would combine them as 'one'
> distributed replicated volume I am unable to guarantee that the files
> that are mirrored are in fact mirrored on servers in the network rather
> than for example two copies on the same physical server.
>
> I have read about 'afr' and 'unify', and its ability of combining each
> different disk with a remote pair.
>
>
> When I read about unify I see:
> "Unify being part of a file system, has a requirement. It will create
> directories on all the child nodes and files in anyone of the child
> nodes. It expects this to be followed properly."
>
> If I take the following setup:
>
> Unify	=>	AFR1	=>  BRICK1a
> 			=>  BRICK1b
> 		AFR2	=>  BRICK2a
> 			=>  BRICK2b
>
> (Where BRICK1a and BRICK2a are in the same server.)
>
>
> Now; what does it mean if a new file/directory is made? It will end up
> in either of BRICK1a/1b or BRICK2a/b? Is the file itself duplicated by
> Unify or only its 'namespace'?
>
>
> Is there any other way to guarantee files are mirrored across servers?
>
>
>
> Stefan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.16 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEAREKAAYFAkzw/mkACgkQYH1+F2Rqwn3m2ACfSflipSFEGrVWMC9N/aszkZ/D
> 3t8An0AxbZaNKt52yXH2Y+IzX9lUQPw7
> =GVNr
> -----END PGP SIGNATURE-----
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users



More information about the Gluster-users mailing list