[gpfsug-discuss] Forcing which node gets expelled?

[Oesterlin, Robert]

If you look at /usr/lpp/mmfs/samples/expelnode.sample you can use this as a base and install this in /var/mmfs/etc on the cluster manager. You can control which of the two nodes get expelled.

We use it here to send an alert when a node is expelled.

There is also "mmexpelnode" which you can force a particular node to be expelled.


Bob Oesterlin
Sr Principal Storage Engineer, Nuance



From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Matt Thorpe <matt.thorpe at bodleian.ox.ac.uk>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Tuesday, October 25, 2016 at 7:05 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: [EXTERNAL] [gpfsug-discuss] Forcing which node gets expelled?

Hi,

We are in the process of diagnosing a networking issue that is causing 2 of our 6 node GPFS cluster to expel each other (it appears they experience a temporary network connection outage and lose contact with each other).  At present it's not consistent which gets expelled by the cluster manager, and I wondered if there was any way to always force a specific node to be expelled in this situation?

Thanks and best regards,
Matt

--------
Matt Thorpe  |  BDLSS Systems Administrator
Bodleian Libraries Osney One Building, Osney Mead, Oxford, OX2 0EW
matt.thorpe at bodleian.ox.ac.uk<mailto:matt.thorpe at bodleian.ox.ac.uk>  |  01865 (2)80027
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=CwICAg&c=djjh8EKwHtOepW4Bjau0lKhLlu-DxM1dlgP0rrLsOzY&r=LPDewt1Z4o9eKc86MXmhqX-45Cz1yz1ylYELF9olLKU&m=Q_f6z64tvENxA9ac7rqWFj2jNd5IrpWEXcynJzHFjz4&s=jqso6xVB-V_zgLba-xjlWwiw3fNRan9NspsVq4PY4nA&e=

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20161025/a473991b/attachment-0002.htm>