Send lustre-discuss mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of lustre-discuss digest..."
Today's Topics:
1. Lustre caching and NUMA nodes (John Bauer)
----------------------------------------------------------------------
Message: 1
Date: Thu, 7 Dec 2023 09:36:00 -0600
From: John Bauer <[email protected]>
To: lustre-discuss <[email protected]>,
[email protected]
Subject: [lustre-discuss] Lustre caching and NUMA nodes
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Peter,
A delayed reply to one more of your questions, "What makes you think
"lustre" is doing that?" , as I had to make another run and gather OSC
stats on all the Lustre file systems mounted on the host that I run dd on.
This host has 12 Lustre file systems, comprised of 507 OSTs. While dd
was running I instrumented the amount of cached data associated with all
507 OSCs.? That is reflected in the bottom frame of the image below.?
Note that in the top frame there was always about 5GB of free memory,
and 50GB of cached data.? I believe it has to be a Lustre issue as the
Linux buffer cache has no knowledge that a page is a Lustre page.? How
is it that every OSC, on all 12 file systems on the host, has its memory
dropped to 0, yet all the other 50GB of cached data on the host remains?
It's as though dropcache is being run on only the lustre file systems.?
My googling around finds no such feature in dropcache that would allow
file system specific dropping.? Is there some tuneable that gives Lustre
pages higher potential for eviction than other cached data?
Another subtle point of interest.? Note that dd writing resumes, as
reflected in the growth of the cached data for its 8 OSTs, before all
the other OSCs have finished dumping.? This is most visible around 2.1
seconds into the run.? Also different is that this dumping phenomenon
happened 3 times in the course of a 10 second run, instead of just 1 as
in the previous run I was referencing, costing this dd run 1.2 seconds.
John
On 12/6/23 14:24, [email protected] wrote:
Send lustre-discuss mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of lustre-discuss digest..."
Today's Topics:
1. Coordinating cluster start and shutdown? (Jan Andersen)
2. Re: Lustre caching and NUMA nodes (Peter Grandi)
3. Re: Coordinating cluster start and shutdown?
(Bertschinger, Thomas Andrew Hjorth)
4. Lustre server still try to recover the lnet reply to the
depreciated clients (Huang, Qiulan)
----------------------------------------------------------------------
Message: 1
Date: Wed, 6 Dec 2023 10:27:11 +0000
From: Jan Andersen<[email protected]>
To: lustre<[email protected]>
Subject: [lustre-discuss] Coordinating cluster start and shutdown?
Message-ID:<[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Are there any tools for coordinating the start and shutdown of lustre
filesystem, so that the OSS systems don't attempt to mount disks before the MGT
and MDT are online?
------------------------------
Message: 2
Date: Wed, 6 Dec 2023 12:40:54 +0000
From:[email protected] (Peter Grandi)
To: list Lustre discussion<[email protected]>
Subject: Re: [lustre-discuss] Lustre caching and NUMA nodes
Message-ID:<[email protected]>
Content-Type: text/plain; charset=iso-8859-1
I have a an OSC caching question.? I am running a dd process
which writes an 8GB file.? The file is on lustre, striped
8x1M.
How the Lustre instance servers store the data may not have a
huge influence on what happens in the client's system buffer
cache.
This is run on a system that has 2 NUMA nodes (? cpu sockets).
[...] Why does lustre go to the trouble of dumping node1 and
then not use node1's memory, when there was always plenty of
free memory on node0?
What makes you think "lustre" is doing that?
Are you aware of the values of the flusher settings such as
'dirty_bytes', 'dirty_ratio', 'dirty_expire_centisecs'?
Have you considered looking at NUMA policies e.g. as described
in 'man numactl'?
Also while you surely know better I usually try to avoid
buffering large amounts of to-be-written data in RAM (whether on
the OSC or the OSS), and to my taste 8GiB "in-flight" is large.
------------------------------
Message: 3
Date: Wed, 6 Dec 2023 16:00:38 +0000
From: "Bertschinger, Thomas Andrew Hjorth"<[email protected]>
To: Jan Andersen<[email protected]>, lustre
<[email protected]>
Subject: Re: [lustre-discuss] Coordinating cluster start and shutdown?
Message-ID:
<ph8pr09mb103611a4b55e420410ae14abaab...@ph8pr09mb10361.namprd09.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello Jan,
You can use the Pacemaker / Corosync high-availability software stack for this:
specifically, ordering constraints [1] can be used.
Unfortunately, Pacemaker is probably over-the-top if you don't need HA -- its
configuration is complex and difficult to get right, and it significantly
complicates system administration. One downside of Pacemaker is that it is not
easy to decouple the Pacemaker service from the Lustre services, meaning if you
stop the Pacemaker service, it will try to stop all of the Lustre services.
This might make it inappropriate for use cases that don't involve HA.
Given those downsides, if others in the community have suggestions on simpler
means to accomplish this, I'd love to see other tools that can be used here
(especially officially supported ones, if they exist).
[1]https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#specifying-the-order-in-which-resources-should-start-stop
- Thomas Bertschinger
________________________________________
From: lustre-discuss<[email protected]> on behalf of Jan
Andersen<[email protected]>
Sent: Wednesday, December 6, 2023 3:27 AM
To: lustre
Subject: [EXTERNAL] [lustre-discuss] Coordinating cluster start and shutdown?
Are there any tools for coordinating the start and shutdown of lustre
filesystem, so that the OSS systems don't attempt to mount disks before the MGT
and MDT are online?
_______________________________________________
------------------------------
Message: 4
Date: Wed, 6 Dec 2023 20:23:11 +0000
From: "Huang, Qiulan"<[email protected]>
To:"[email protected]"
<[email protected]>
Cc: "Huang, Qiulan"<[email protected]>
Subject: [lustre-discuss] Lustre server still try to recover the lnet
reply to the depreciated clients
Message-ID:
<blapr09mb685012e0f741e1b98f65f8c6ce...@blapr09mb6850.namprd09.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello all,
We removed some clients two weeks ago but we see the Lustre server is still
trying to handle the lnet recovery reply to those clients (the error log is
posted as below). And they are still listed in the exports dir.
I tried to run to evict the clients but failed with the error "no exports
found"
lctl set_param mdt.*.evict_client=10.68.178.25@tcp
Do you know how to clean up the removed the depreciated clients? Any
suggestions would be greatly appreciated.
For example:
[root@mds2 ~]# ll /proc/fs/lustre/mdt/data-MDT0000/exports/10.67.178.25@tcp/
total 0
-r--r--r-- 1 root root 0 Dec 5 15:41 export
-r--r--r-- 1 root root 0 Dec 5 15:41 fmd_count
-r--r--r-- 1 root root 0 Dec 5 15:41 hash
-rw-r--r-- 1 root root 0 Dec 5 15:41 ldlm_stats
-r--r--r-- 1 root root 0 Dec 5 15:41 nodemap
-r--r--r-- 1 root root 0 Dec 5 15:41 open_files
-r--r--r-- 1 root root 0 Dec 5 15:41 reply_data
-rw-r--r-- 1 root root 0 Aug 14 10:58 stats
-r--r--r-- 1 root root 0 Dec 5 15:41 uuid
/var/log/messages:Dec 6 12:50:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 13:05:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.178.25@tcp) recovery failed with -110
/var/log/messages:Dec 6 13:05:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 13:20:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.178.25@tcp) recovery failed with -110
/var/log/messages:Dec 6 13:20:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 13:35:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.178.25@tcp) recovery failed with -110
/var/log/messages:Dec 6 13:35:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 13:50:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.178.25@tcp) recovery failed with -110
/var/log/messages:Dec 6 13:50:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 14:05:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.178.25@tcp) recovery failed with -110
/var/log/messages:Dec 6 14:05:17 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 14:20:16 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.178.25@tcp) recovery failed with -110
/var/log/messages:Dec 6 14:20:16 mds2 kernel: LNetError:
11579:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 1 previous
similar message
/var/log/messages:Dec 6 14:30:17 mds2 kernel: LNetError:
3806712:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.176.25@tcp) recovery failed with -111
/var/log/messages:Dec 6 14:30:17 mds2 kernel: LNetError:
3806712:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 3 previous
similar messages
/var/log/messages:Dec 6 14:47:14 mds2 kernel: LNetError:
3812070:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.176.25@tcp) recovery failed with -111
/var/log/messages:Dec 6 14:47:14 mds2 kernel: LNetError:
3812070:0:(lib-move.c:4005:lnet_handle_recovery_reply()) Skipped 8 previous
similar messages
/var/log/messages:Dec 6 15:02:14 mds2 kernel: LNetError:
3817248:0:(lib-move.c:4005:lnet_handle_recovery_reply()) peer NI
(10.67.176.25@tcp) recovery failed with -111
Regards,
Qiulan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:<http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20231206/89b7c124/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
lustre-discuss mailing list
[email protected]
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
------------------------------
End of lustre-discuss Digest, Vol 213, Issue 7
**********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20231207/ce8919f0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pfe27_allOSC_cached.png
Type: image/png
Size: 12394 bytes
Desc: not available
URL:
<http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20231207/ce8919f0/attachment.png>
------------------------------
Subject: Digest Footer
_______________________________________________
lustre-discuss mailing list
[email protected]
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
------------------------------
End of lustre-discuss Digest, Vol 213, Issue 10
***********************************************
