Hi Lucia,
I think that was your solution. So, two questions a) do any of the plugins
you use also use Globus and b) what is the version of your Lustre?
Is the answer to (a) is yes then this is indeed your solution as it is
known that Globus is incompatible with async I/O. Also, depending on the
version of the Lustre being used, it may also be incompatible with async
I/O.
Andy
On Thu, 1 Dec 2022, lmorganti wrote:
> Hi Andy,
> we did turn off async i/o in two of the 4 CMS servers 20 days ago.
> Since then, we never observed thread saturation, neither in those 2 servers nor in the 2 with async i/o on.
> So unfortunately we cannot comment further at the moment.
> Lucia
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1799#issuecomment-1333453644
> You are receiving this because you were assigned.
>
> Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
Message ID: <xrootd/xrootd/issues/1799/1334026264@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1799#issuecomment-1334026264",
"url": "https://github.com/xrootd/xrootd/issues/1799#issuecomment-1334026264",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
