 |
 |
To reproduce the issue it's enough to set a very high RLIMIT_NOFILE. For example ``` ulimit -n 1073741816 ``` This value, for example, results in xrootd consuming 10+ Gb of ram. xrootd uses https://github.com/xrootd/xrootd/blob/aaf638df423f22cee3a09aba76febcc7152ef34b/src/Xrd/XrdConfig.cc#L1191 this value to set the actual poller size. https://github.com/xrootd/xrootd/blob/aaf638df423f22cee3a09aba76febcc7152ef34b/src/Xrd/XrdPollE.icc#L44 The ulimit value shouldn't be used blindly without any upper bound and/or configuration parameter allowing the user to explicitly set the desired upper bound. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1962 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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