Re: Different network for server and client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>I thought about this, but if servers are also clients, then this would not work.
Well, I suppose this is not possible or not required.

In that case not sure why would you need separate network ?


>>Is it really the client which replicates the data and distributes it to the different nodes?

Yes, as far as I understand, folks can correct me here. When you mount the GlusterFS fuse, it gets the list of storage nodes which are part of the volume brick. If you write your data on the client, the GlusterFS fuse client sends it to the server based on whatever translation service is chosen, example replicated, distributed, dispersed volume.

--
Deepak

> On Feb 22, 2017, at 9:44 AM, Alessandro Briosi <ab1@xxxxxxxxxxx> wrote:
> 
> 
> I thought about this, but if servers are also clients, then this would not work.
> Well, I suppose this is not possible or not required.
> 
> Is it really the client which replicates the data and distributes it to the different nodes?
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux