Re: [Gluster-users] Replicated Volume (mirror) on 17 nodes.
https://joejulian.name/blog/glusterfs-replication-dos-and-donts/ On 02/24/2016 01:34 PM, Simone Taliercio wrote: Hi all :) I would need soon to create a pool of 17 nodes. Each node requires a copy of the same file "locally" so that can be accessed from the deployed application. * Do you see any performance issue in creating a Replica Set on 17 nodes ? Any best practice that I should follow ? * An other question: in case there's no problem then on this line gluster volume create gv0 replica*2* server1:/data/brick1/gv0 server2:/data/brick1/gv0 do i need to provide 17 instead of 2 ? Sorry for my basic questions. Thanks a lot for your support! Simone ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Replicated Volume (mirror) on 17 nodes.
On 02/24/2016 04:34 PM, Simone Taliercio wrote: > Hi all :) > > I would need soon to create a pool of 17 nodes. Each node requires a > copy of the same file "locally" so that can be accessed from the > deployed application. > > * Do you see any performance issue in creating a Replica Set on 17 nodes > ? Any best practice that I should follow ? > > * An other question: in case there's no problem then on this line > > gluster volume create gv0 replica*2* server1:/data/brick1/gv0 > server2:/data/brick1/gv0 > > do i need to provide 17 instead of 2 ? Yes, you'll need to provide _all_ the bricks participating in the volume. It will be hard to get a "replica 2" volume with an odd number of bricks. You will need to rethink that part of your solution. -- Kaleb ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Replicated Volume (mirror) on 17 nodes.
2016-02-25 9:20 GMT+01:00 Ravishankar N : > Right. You can mount the replica 3 volume that you just created on any node. > Like I said it's just like accessing a remote share. Except that the 'share' > is a glusterfs volume that you just created. > If I understand your use case correctly, you would need to create a > glusterfs volume based on 3 EC2 instances and then mount the volume on all > of the (17?) instances on which your application runs. Thanks again Ravi! I think now everything it makes sense. I hope to have the 17 nodes soon in order to test 3+1 setup asap :) Fingers crossed! Best, Simone ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Replicated Volume (mirror) on 17 nodes.
Hello, On 02/25/2016 11:42 AM, Simone Taliercio wrote: Hi Ravi, Thanks a lot for your prompt reply! 2016-02-25 6:07 GMT+01:00 Ravishankar N : I don't know what your use case is but I don't think you want to create so many replicas. I need to scale my application on multiple nodes because we have to tackle an high number of requests per second. The application is hosted on AWS EC2 instances and each one uses EBS. Each instance needs to read some local files. That's why I'm currently replicating all the files on each instance. So far I had max 3 nodes. Why not just create a glusterfs volume of replica-2 or replica-3 or even an arbiter volume, and mount them on all 17 nodes? Here I'm definitely missing some basics (sorry for that): what are the steps to set-up 3-replicas (+1 arbiter) but still allow all 17 nodes to retrieve the files ? The steps are almost the same as replica -3, except for a small change in the syntax: `gluster volume create replica 3 arbiter 1 ` Are they transferred on demands over the network ? It's just like accessing an NFS share. You mount the volume on any machine and you can perform I/O. So far I followed those steps: - mount an empty "hard disk" to the instance - format it in xfs - create directory for one brick - add peers - create 1 volume with "... replica 3 " - mount the volume on a specific path And then I can see one file that is created on one machine being replicated on all the others. I have a limited vision at this use case Right. You can mount the replica 3 volume that you just created on any node. Like I said it's just like accessing a remote share. Except that the 'share' is a glusterfs volume that you just created. If I understand your use case correctly, you would need to create a glusterfs volume based on 3 EC2 instances and then mount the volume on all of the (17?) instances on which your application runs. HTH, Ravi :-/ I think replica 4 is what some people in the community have used at the max but even that is an overkill IMO. Help :) Thanks, Simone Regards, Ravi ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Replicated Volume (mirror) on 17 nodes.
Hi Ravi, Thanks a lot for your prompt reply! 2016-02-25 6:07 GMT+01:00 Ravishankar N : > I don't know what your use case is but I don't think you want to create so > many replicas. I need to scale my application on multiple nodes because we have to tackle an high number of requests per second. The application is hosted on AWS EC2 instances and each one uses EBS. Each instance needs to read some local files. That's why I'm currently replicating all the files on each instance. So far I had max 3 nodes. > Why not just create a glusterfs volume of replica-2 or replica-3 or even an > arbiter volume, and mount them on all 17 nodes? Here I'm definitely missing some basics (sorry for that): what are the steps to set-up 3-replicas (+1 arbiter) but still allow all 17 nodes to retrieve the files ? Are they transferred on demands over the network ? So far I followed those steps: - mount an empty "hard disk" to the instance - format it in xfs - create directory for one brick - add peers - create 1 volume with "... replica 3 " - mount the volume on a specific path And then I can see one file that is created on one machine being replicated on all the others. I have a limited vision at this use case :-/ > > I think replica 4 is what some people in the community have used at the max > but even that is an overkill IMO. Help :) Thanks, Simone > > Regards, > Ravi > > > > ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Replicated Volume (mirror) on 17 nodes.
On 02/25/2016 03:09 AM, Simone Taliercio wrote: Hi all :) I would need soon to create a pool of 17 nodes. Each node requires a copy of the same file "locally" so that can be accessed from the deployed application. * Do you see any performance issue in creating a Replica Set on 17 nodes ? Any best practice that I should follow ? * An other question: in case there's no problem then on this line gluster volume create gv0 replica* 2* server1:/data/brick1/gv0 server2:/data/brick1/gv0 do i need to provide 17 instead of 2 ? I don't know what your use case is but I don't think you want to create so many replicas. Why not just create a glusterfs volume of replica-2 or replica-3 or even an arbiter volume, and mount them on all 17 nodes? I think replica 4 is what some people in the community have used at the max but even that is an overkill IMO. Regards, Ravi Sorry for my basic questions. Thanks a lot for your support! Simone ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users