Gluster users - Jan 2017 - Convert to Shard - Setting Guidance

On 20/01/2017 1:11 PM, Gustave Dahl wrote:
>
> One: It may take months to convert my current VM images to shard?s, do 
> you see any issues with this?  My priority is to make sure future 
> images are distributed as shards.
>
> Two:  Settings, my intent is to set it as follows based on guidance on 
> the Redhat site and what I have been reading here.  Do these look 
> okay?  Additional suggestions?
>
They look good to me, except I would go with a smaller chunksize, but 
like Kevin, I don't have 10G ethernet or SSD bricks  (Jellus). You do 
get slightly better write performance with the larger shard sizes.


One question - how do you plan to convert the VM's?

- setup a new volume and copy the VM images to that?

- or change the shard setting inplace? (I don't think that would work)

--
Lindsay Mathieson

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170121/aea76a94/attachment.html>

> - or change the shard setting inplace? (I don't think that would work)
It will only affect new files, so you'll need to copy the current images
to new names. That's why I was speaking about livre migrating the disk
to the same volume, that's how I did it last year.

-- 
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Digital signature
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170120/540468f8/attachment.sig>

> If your images easily fit within the bricks, why do you need sharding in
>> the first place? It adds an extra layer of complexity & removes the
cool
>> feature of having entire files on each brick, making DR & things a
lot
>> easier.
>
>
> Because healing with large VM images completes orders of magnitude faster
> and consumes far less bandwidth/cpu/disk IO
>
Isn't that only the case with full, non-granular heals? And according to
the docs, "full" forces a resync of the entire volume, not just the
out-of-sync files. Seems a bit overkill for anything other than a brick
replacement...


One question - how do you plan to convert the VM's?
>
> - setup a new volume and copy the VM images to that?
>
> - or change the shard setting inplace? (I don't think that would work)
>
AFAIK, if you enable sharding on a volume, it will only apply to new files.
An easier option might be to enable sharding & then clone the VMs to create
new VHDs.

Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170120/c4ce3d4d/attachment.html>