 |
 |
Hi everybody, As things scale up there are more and more cases where users' jobs get -9 killed by the batch system (or by the user realizing they did something stupid). Servers know nothing about this as xrootd never checks the sockets to see if there's anybody still at the other end. Consequentially, monitoring thinks the file is still open ... the inactivity cut off I have in XrdMon collector is 1 day! Whatever happens, the close time is wildly off. At the moment I have like 80% of open files on collector in this state ... close to 10,000 coming just form EOS at FNAL. Grrr, etc. Does it make sense to add a configuration option to make servers perform aliveness checks on connected clients? I know, client applications should be shutdown properly ... Best, Matevz ######################################################################## 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