[gpfsug-discuss] Compatibility question

[Simon Thompson]

My guess would be rhel6 clients. Though rhel6 should be able to run a 4.x release and then you are N-1.

Our one and only remaining centos6 box, well we unceremoniously kicked that out of the cluster and made it use NFS.

Simon

From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of "luke.raimbach at googlemail.com" <luke.raimbach at googlemail.com>
Reply to: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Date: Friday, 22 November 2019 at 01:12
To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Compatibility question

That would make my eyes water and maybe fall out. Yours might too of you try it.

Be very careful with v3 upgrades, especially going up to v5 directly.

You will certainly run into RPC incompatibility problems with the v3 and v5 nodes running concurrently. Staying within the supported envelope of "one major version" difference will ease the raising of support tickets with IBM if you run into problems.

Why can't you upgrade the clients?

On Thu, 21 Nov 2019, 18:24 George Terry, <gterryc at vmsupport.com<mailto:gterryc at vmsupport.com>> wrote:
Hello,

I have a question about compatibility between two different versions. I have a cluster with 6 gpfs nodes. 2 of them are NSD servers the other 4 are clientes nodes. I will upgrade the NSD servers from 3.5.0 to 5.0.3.  Due to application's  issues I cannot update the client nodes. So, my question is, can i have a cluster with client nodes with 3.5.0.7 version and the NSD nodes in 5.0.3 version with de filesystem in 3.5.0.7 (13.23) version?

Thanks for the support.

George
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org<http://spectrumscale.org>
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191122/e1f66d07/attachment-0002.htm>