Hi, thanks for the suggestions. I'll open a PR that removes the UnregisterTask (I hope this will fix the original problem). I think the point about removing the tick generator to simplify is fair.

This Tick is being used to do the request timeout check. But it appears this could be driven from the Event loop (where we have an event at least as often) from a poller thread. But there could easily be there are some complications; Maybe it takes too long or we'd run into some deadlocks simply moving it to the Poll thread. I don't know if @simonmichal has a strong opinion on that, or has tried it like that previously -- perhaps we could open a second issue to get that looked at on the longer timeframe. (Assuming the original problem is solved in the meantime, I believe when this issue happens in production it is not very good as the fuse fs on a machine is hung; although it didn't happen very much in the last few weeks @Einscrew )

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1883#issuecomment-1458502511", "url": "https://github.com/xrootd/xrootd/issues/1883#issuecomment-1458502511", "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