1:06 p.m.
I understand that Genesha supports HA configurations. Software upgrades are a lot more
frequent than hardware failures. The ability to do upgrades is actually more of a
motivation for HA than handling failures. Do you support rolling upgrades, i.e. upgrading
one node while the other is active? That would require that the two nodes would end up
with different versions for at least some period of time.
1:17 p.m.
Hi,
To the best of my knowledge there's no reason why a rolling upgrade
wouldn't work seamlessly.
There's nothing version specific about the recovery and no reason I'm aware
of that differing versions of ganesha wouldn't work side by side in an HA
cluster over the course of an upgrade.
I suggest you play it safe and try it in a non-production environment
before doing it on a production system.
HTH.
On Thu, Nov 21, 2019 at 2:07 PM Charles Hedrick <hedrick(a)rutgers.edu> wrote:
I understand that Genesha supports HA configurations. Software
upgrades
are a lot more frequent than hardware failures. The ability to do upgrades
is actually more of a motivation for HA than handling failures. Do you
support rolling upgrades, i.e. upgrading one node while the other is
active? That would require that the two nodes would end up with different
versions for at least some period of time.
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
1:34 p.m.
Expanding on that, the information we save for recovery hasn't changed
in a while, so upgrades should be fine. However, make sure you do an
unclean shutdown of the Ganesha to be upgraded (e.g., kill -9 rather
than kill) since a clean shutdown will clean up all the state/locks/open
files and so on, making recovery by active clients impossible.
Daniel
On 11/21/19 2:17 PM, Kaleb Keithley wrote:
Hi,
To the best of my knowledge there's no reason why a rolling upgrade
wouldn't work seamlessly.
There's nothing version specific about the recovery and no reason I'm
aware of that differing versions of ganesha wouldn't work side by side
in an HA cluster over the course of an upgrade.
I suggest you play it safe and try it in a non-production environment
before doing it on a production system.
HTH.
On Thu, Nov 21, 2019 at 2:07 PM Charles Hedrick <hedrick(a)rutgers.edu
<mailto:hedrick@rutgers.edu>> wrote:
I understand that Genesha supports HA configurations. Software
upgrades are a lot more frequent than hardware failures. The
ability to do upgrades is actually more of a motivation for HA
than handling failures. Do you support rolling upgrades, i.e.
upgrading one node while the other is active? That would require
that the two nodes would end up with different versions for at
least some period of time.
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
<mailto:support@lists.nfs-ganesha.org>
To unsubscribe send an email to
support-leave(a)lists.nfs-ganesha.org
<mailto:support-leave@lists.nfs-ganesha.org>
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
8:33 a.m.
Even a graceful shutdown should work fine unless there are some bugs in the
shutdown path. The client should NOT use "soft" mount option though. We
have used graceful shutdown (with GPFS fsal), and didn't encounter any
issue yet.
On Fri, Nov 22, 2019 at 1:06 AM Daniel Gryniewicz <dgryniew(a)redhat.com>
wrote:
Expanding on that, the information we save for recovery hasn't
changed
in a while, so upgrades should be fine. However, make sure you do an
unclean shutdown of the Ganesha to be upgraded (e.g., kill -9 rather
than kill) since a clean shutdown will clean up all the state/locks/open
files and so on, making recovery by active clients impossible.
Daniel
On 11/21/19 2:17 PM, Kaleb Keithley wrote:
> Hi,
>
> To the best of my knowledge there's no reason why a rolling upgrade
> wouldn't work seamlessly.
>
> There's nothing version specific about the recovery and no reason I'm
> aware of that differing versions of ganesha wouldn't work side by side
> in an HA cluster over the course of an upgrade.
>
> I suggest you play it safe and try it in a non-production environment
> before doing it on a production system.
>
> HTH.
>
>
>
>
> On Thu, Nov 21, 2019 at 2:07 PM Charles Hedrick <hedrick(a)rutgers.edu
> <mailto:hedrick@rutgers.edu>> wrote:
>
> I understand that Genesha supports HA configurations. Software
> upgrades are a lot more frequent than hardware failures. The
> ability to do upgrades is actually more of a motivation for HA
> than handling failures. Do you support rolling upgrades, i.e.
> upgrading one node while the other is active? That would require
> that the two nodes would end up with different versions for at
> least some period of time.
> _______________________________________________
> Support mailing list -- support(a)lists.nfs-ganesha.org
> <mailto:support@lists.nfs-ganesha.org>
> To unsubscribe send an email to
> support-leave(a)lists.nfs-ganesha.org
> <mailto:support-leave@lists.nfs-ganesha.org>
>
>
> _______________________________________________
> Support mailing list -- support(a)lists.nfs-ganesha.org
> To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
2065
days inactive
2066
days old
3 comments
4 participants
participants (4)
-
Charles Hedrick -
Daniel Gryniewicz -
Kaleb Keithley -
Malahal Naineni