On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P wrote:
> if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access
> volume without any challenge?
>
> I am asking this because 4.0 comes with DHT2?
Very short answer, yes. Your volumes will remain the same. And you
will continue to access t
On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P wrote:
> if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access
> volume without any challenge?
>
> I am asking this because 4.0 comes with DHT2?
>
>
Thanks for bringing this up. We did hear such concerns earlier too.
Multiple things her
Hi Amudhan,
Please go through the following that would clarify up-gradation concerns
from DHT to RIO in 4.0
1. RIO would not deprecate DHT. Both DHT and RIO would co-exist.
2. DHT volumes would not be migrated to RIO. DHT volumes would still be
using DHT code.
3. The new volume creat
if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access
volume without any challenge?
I am asking this because 4.0 comes with DHT2?
On Thu, Nov 2, 2017 at 2:26 PM, Kaushal M wrote:
> We're fast approaching the time for Gluster-4.0. And we would like to
> set out the expected
does RIO improves folder listing and rebalance, when compared to 3.x?
if yes, do you have any performance data comparing RIO and DHT?
On Thu, Nov 2, 2017 at 4:12 PM, Kaushal M wrote:
> On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P wrote:
> > if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be
On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic wrote:
> Will the various client packages (centos in my case) be able to
> automatically handle the upgrade vs new install decision, or will we be
> required to do something manually to determine that?
We should be able to do this with CentOS (and oth
Just so I am clear the upgrade process will be as follows:
upgrade all clients to 4.0
rolling upgrade all servers to 4.0 (with GD1)
kill all GD1 daemons on all servers and run upgrade script (new clients
unable to connect at this point)
start GD2 ( necessary or does the upgrade script do this?)
On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil wrote:
> Just so I am clear the upgrade process will be as follows:
>
> upgrade all clients to 4.0
>
> rolling upgrade all servers to 4.0 (with GD1)
>
> kill all GD1 daemons on all servers and run upgrade script (new clients
> unable to connect at this
Ahh OK I see, thanks
On 6 November 2017 at 00:54, Kaushal M wrote:
> On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil
> wrote:
> > Just so I am clear the upgrade process will be as follows:
> >
> > upgrade all clients to 4.0
> >
> > rolling upgrade all servers to 4.0 (with GD1)
> >
> > kill all G
Will the various client packages (centos in my case) be able to automatically
handle the upgrade vs new install decision, or will we be required to do
something manually to determine that?
It’s a little unclear that things will continue without interruption because of
the way you describe the c
10 matches
Mail list logo
