[gpfsug-discuss] CCR database inconsistent
Uwe Falke
uwe.falke at kit.edu
Tue Jun 13 15:46:55 BST 2023
Dear all.
it seems we have a (minor?) inconsistency in the CCR database of one of
our clusters.
A quorum node was set to nonquorum. Be it node A.
Another node was designated as quorum node. Be it Node N.
The other two quorum nodes, B and C, were left untouched.
Then, node A has been removed (which was not reachable by ssh at that
time). Now, on three of the remaining 6 nodes, the removed node A is
still contained in the `mmccr dump` output along with nodes B and C
while on the other 3 nodes that command lists the three current quorum
nodes B, C, and N properly.
mmccr lsnodes returns the proper list (B, C , N) on all 6 remaining nodes.
Any idea how to get this straight?
The nodes still thinking node A is part of the CCR node collective try
to connect to the gone node A periodically for mmhealth stuff.
Many thanks in advance
Uwe
--
Karlsruhe Institute of Technology (KIT)
Steinbuch Centre for Computing (SCC)
Scientific Data Management (SDM)
Uwe Falke
Hermann-von-Helmholtz-Platz 1, Building 442, Room 187
D-76344 Eggenstein-Leopoldshafen
Tel: +49 721 608 28024
Email: uwe.falke at kit.edu
www.scc.kit.edu
Registered office:
Kaiserstraße 12, 76131 Karlsruhe, Germany
KIT – The Research University in the Helmholtz Association
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5814 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20230613/618ad905/attachment.bin>
More information about the gpfsug-discuss
mailing list