<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
Following on from Jonathan Buzzards comments, I'd also like to point out that I've never known a central DNS failure in a UK HEI for as long as I can remember, and it was certainly not my intention to suggest that as I think a central DNS issue is highly unlikely.
And indeed, as I originally noted, the standard command-line tools on the nodes resolve the names as expected, so whatever is going on looks like it affects GPFS only. It may even be that the repetition of the domain names in the logs is just a function of
something it is doing when logging when a node is failing to connect for some other reason entirely. It's just not something I recall having seen before and wanted to see if anyone else had seen it.</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> gpfsug-discuss-bounces@spectrumscale.org <gpfsug-discuss-bounces@spectrumscale.org> on behalf of Jonathan Buzzard <jonathan.buzzard@strath.ac.uk><br>
<b>Sent:</b> 09 May 2020 23:22<br>
<b>To:</b> gpfsug-discuss@spectrumscale.org <gpfsug-discuss@spectrumscale.org><br>
<b>Subject:</b> Re: [gpfsug-discuss] Odd networking/name resolution issue</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On 09/05/2020 12:06, Jaime Pinto wrote:<br>
> DNS shouldn't be relied upon on a GPFS cluster for internal <br>
> communication/management or data.<br>
> <br>
<br>
The 1980's have called and want their lack of IP resolution protocols <br>
back :-)<br>
<br>
I would kindly disagree. If your DNS is not working then your cluster is <br>
fubar anyway and a zillion other things will also break very rapidly. <br>
For us at least half of the running jobs would be dead in a few minutes <br>
as failure to contact license servers would cause the software to stop. <br>
All authentication and account lookup is also going to fail as well.<br>
<br>
You could distribute a hosts file but frankly outside of a storage only <br>
cluster (as opposed to one with hundreds if not thousands of compute <br>
nodes) that is frankly madness and will inevitably come to bite you in <br>
the ass because they *will* get out of sync. The only hosts entry we <br>
have is for the Salt Stack host because it tries to do things before the <br>
DNS resolvers have been setup and consequently breaks otherwise. Which <br>
IMHO is duff on it's behalf.<br>
<br>
I would add I can't think of a time in the last 16 years where internal <br>
DNS at any University I have worked at has stopped working for even one <br>
millisecond. If DNS is that flaky at your institution then I suggest <br>
sacking the people responsible for it's maintenance as being incompetent <br>
twits. It is just such a vanishingly remote possibility that it's not <br>
worth bothering about. Frankly a aircraft falling out the sky and <br>
squishing your data centre seems more likely to me.<br>
<br>
Finally in a world of IPv6 then anything other than DNS is a utter <br>
madness IMHO.<br>
<br>
<br>
JAB.<br>
<br>
-- <br>
Jonathan A. Buzzard Tel: +44141-5483420<br>
HPC System Administrator, ARCHIE-WeSt.<br>
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at spectrumscale.org<br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>
</div>
</span></font></div>
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
</body>
</html>