On 10/05/2020 14:28, Jaime Pinto wrote:
The rationale for my suggestion doesn't have much to do with the central
DNS server, but everything to do with the DNS client side of the service.
If you have a very busy cluster at times, and a number of nodes really
busy with 1000+ IOPs for instance, so
Aaron,
Not sure if this matches your symptoms precisely, but this appears to be the same problem as the one fixed in
https://www.ibm.com/support/pages/apar/IV93896
(fixed in 5.0.2.0 / 4.2.3.13)
This particular problem/fix above did not cause nodes to be expelled. It "just" affected how the
: Jaime Pinto
> To: gpfsug main discussion list ,
> TURNER Aaron
> Date: 05/10/2020 09:28 AM
> Subject: [EXTERNAL] Re: [gpfsug-discuss] Odd networking/name resolution
> issue
> Sent by: gpfsug-discuss-boun...@spectrumscale.org
> --
>
>
>
&g
,
TURNER Aaron
Date: 05/10/2020 09:28 AM
Subject:[EXTERNAL] Re: [gpfsug-discuss] Odd networking/name resolution
issue
Sent by:gpfsug-discuss-boun...@spectrumscale.org
The rationale for my suggestion doesn't have much to do with the central
DNS server
of Jonathan Buzzard
*Sent:* 09 May 2020 23:22
*To:* gpfsug-discuss@spectrumscale.org
*Subject:* Re: [gpfsug-discuss] Odd networking/name resolution issue
On 09/05/2020 12:06, Jaime Pinto wrote:
DNS shouldn't be relied upon on a GPFS cluster for internal
communication/management or data.
The 1980's
@spectrumscale.org
Subject: Re: [gpfsug-discuss] Odd networking/name resolution issue
On 09/05/2020 12:06, Jaime Pinto wrote:
> DNS shouldn't be relied upon on a GPFS cluster for internal
> communication/management or data.
>
The 1980's have called and want their lack of IP resolution protocols
ba
On 09/05/2020 12:06, Jaime Pinto wrote:
DNS shouldn't be relied upon on a GPFS cluster for internal
communication/management or data.
The 1980's have called and want their lack of IP resolution protocols
back :-)
I would kindly disagree. If your DNS is not working then your cluster is
DNS shouldn't be relied upon on a GPFS cluster for internal
communication/management or data.
As a starting point, make sure the IP's and names of all managers/quorum nodes
and clients have *unique* entries in the hosts files of all other nodes in the
clusters, being the same as how they
Dear All,
We are getting, on an intermittent basis with currently no obvious pattern, an
issue with GPFS nodes reporting rejecting nodes of the form:
nodename.domain.domain.domain
DNS resolution using the standard command-line tools of the IP address present
in the logs does not repeat