[Gluster-users] Should I be using gluster 3 or gluster 4?

[Vlad Kopylov]

Tiering is working on 3.12.4
For the small file load it didn't work for us because of excessive attr
calls. After adding ssd tier all speeds for small file load doubled.
On small file load the bottle neck appears to be the network. Unless you
have 10G local cluster with RDMA you will probably get same results.

Just tune volume for small file access.

v

On Tue, Nov 6, 2018 at 2:04 AM Jeevan Patnaik <g1patnaik at gmail.com> wrote:

> Hi,
>
> We are doing production deployment ande I have tested 3.12.4 and found
> okay to proceed. But we have decided to use tiering feature at the last
> minute. But something is not right or missing with tiering feature in
> 3.12.4 and hence, I'm thinking of using higher versions which may have
> fixed bugs with tiering. But we don't have enough time to test it
> completely for other possible issues for production deployment. So, I'm
> checking for a safest version with stable tiering feature.
>
> Consolidating the files to a backup storage and restoring them is not
> efficient or feasible option for us, as we have terabytes of small file
> data which can take huge times..so, downgrading or upgrading is something
> we can't do so often but only with a scheduled downtime. Hence, trying
> version 5 and falling back is not preferred option for us.
>
>
> Regards,
> Jeevan.
>
>
> On Tue, Nov 6, 2018, 12:24 PM Jeevan Patnaik <g1patnaik at gmail.com> wrote:
>
>> Hi Vlad,
>>
>> I'm still confused of gluster releases. :(
>> Is 3.13 an official gluster release? It's not mentioned in
>> www.gluster.org/release-schedule
>>
>> Which is more stable 3.13.2 or 3.12.6 or 4.1.5?
>>
>> 3.13.2 was released in Jan and no minor releases since then..So, I expect
>> it's a stable release. or maybe noone has used it enough to report bugs?
>>
>> I understand we may see bugs even in the most stable version while using
>> it. I'm looking for a version thats safe to use with least chance of
>> corrupting or loosing our files.
>>
>> I'm set to test 3.13.2 tiering feature, but have my thoughts about if
>> 3.12.6 or 4.1.5 should be tested instead.
>>
>> Regards,
>> Jeevan.
>>
>>
>> On Nov 4, 2018 5:11 AM, "Vlad Kopylov" <vladkopy at gmail.com> wrote:
>>
>> If you doing replica - start with 5, run your load on it. You can always
>> fallback to 3.12 or 4. It is not like your files will be gone.
>> With distributed might be harder, files will still be on the bricks but
>> you will have to consolidate them or copy in to new volume after downgrade.
>> Documentation is all the same.
>>
>>
>> v
>>
>> On Wed, Oct 31, 2018 at 2:54 AM Jeevan Patnaik <g1patnaik at gmail.com>
>> wrote:
>>
>>> Hi Vlad,
>>>
>>> Can gluster 4.1.5 too be used for production? There's no documentation
>>> for gluster 4.
>>>
>>> Regards,
>>> Jeevan.
>>>
>>> On Wed, Oct 31, 2018, 9:37 AM Vlad Kopylov <vladkopy at gmail.com> wrote:
>>>
>>>> 3.12.14 working fine in production for file access
>>>> you can find vol and mount settings in mailing list archive
>>>>
>>>> On Tue, Oct 30, 2018 at 11:05 AM Jeevan Patnaik <g1patnaik at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I see gluster 3 has reached end of life and gluster 5 has just been
>>>>> introduced.
>>>>>
>>>>> Is gluster 4.1.5 stable enough for production deployment? I see by
>>>>> default gluster docs point  to v3  only  and there  are no gluster docs
>>>>> for 4 or 5.  Why so? And I'm mainly looking for a stable gluster tiering
>>>>> feature and Kernek NFS support. I faced few issues with tiering in 3.14 and
>>>>> so thinking if I should switch to 4.1.5, as it will be a production
>>>>> deployment.
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Regards,
>>>>> Jeevan.
>>>>> _______________________________________________
>>>>> Gluster-users mailing list
>>>>> Gluster-users at gluster.org
>>>>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>>>
>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20181106/db071e90/attachment.html>