Gluster users - Sep 2016 - Production cluster planning

On Tue, Sep 20, 2016 at 3:24 PM, Gandalf Corvotempesta <
gandalf.corvotempesta at gmail.com> wrote:
> 2016-09-20 10:28 GMT+02:00 Pranith Kumar Karampuri <pkarampu at
redhat.com>:
> > Are you willing to take VM snapshots at the right times?
>
> Yes, sure.
>
> In addition, the same cluster would also be used to store files shared
> between webservers, like the uploaded images and so on.
>
I would suggest to use separate volumes for this, because the optimizations
for VM image store on the volume would slow things down for webservers kind
of workload IMHO. Most of the perf xlators should be disabled in VM image
store usecase.

>
> > Please don't use EC for Random write workload, it is better for
extending
> > write workload at the moment. Replica 3/Arbiter is what I would
suggest.
>
> With replica 3/arbiter do you mean 3 hosts in replica plus an arbitrer
> or 2 hosts in replica plus an arbiter?
>
2hosts in replica plus arbiter.

-- 
Pranith
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160920/ea41cc9d/attachment.html>

2016-09-20 11:57 GMT+02:00 Pranith Kumar Karampuri <pkarampu at
redhat.com>:
> I would suggest to use separate volumes for this, because the optimizations
> for VM image store on the volume would slow things down for webservers kind
> of workload IMHO. Most of the perf xlators should be disabled in VM image
> store usecase.
Different volumes means different bricks/disks, right?
So, if I would like to have all replicated 3 times (1 disk per server)
with 2 volumes, i have to put at least 2 disks per server?
> 2hosts in replica plus arbiter.
Any differences between replica2 + arbiter or replica3 without arbiter?
Replica 3 should be more safe, as data are replicated 3 times.