[gpfsug-discuss] mm'add|del'node with ccr enabled

[Oesterlin, Robert]

Yes, there were issues with this in pre 4.2? versions of GPFS. My clusters are at 4.2.2 with CCR (working my way to 4.2.3-5) and I’ve been using this process on my quorum nodes when I need to update them:

mmchnode –quorum -N new-node (designate a new quorum node, going from 3 to 4)
mmchnode –nonquorum -N old-node (remove existing node to be updated)

I can then shutdown “old-node” and then when I bring it back up, I reverse the process. I’ve had no issues using this process.


Bob Oesterlin
Sr Principal Storage Engineer, Nuance

From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of "J. Eric Wonderley" <eric.wonderley at vt.edu>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Friday, December 8, 2017 at 10:11 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: [EXTERNAL] [gpfsug-discuss] mm'add|del'node with ccr enabled

Hello:

If I recall correctly this does not work...correct?  I think the last time I attempted this was gpfs version <=4.1.  I think I attempted to add a quorum node.

The process was that I remember doing was mmshutdown -a, mmchcluster --ccr-disable, mmaddnode yadayada, mmchcluster --ccr-enable, mmstartup.

I think with ccr disabled mmaddnode can be run with gpfs up.  We would like to run with ccr enabled but it does make adding/removing nodes unpleasant.

Would this be required of a non-quorum node?

Any changes concerning this with gpfs version >=4.2?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171208/da944b42/attachment.htm>