westonpace commented on pull request #12099: URL: https://github.com/apache/arrow/pull/12099#issuecomment-1007663490
Moving the Close/Wait to the I/O thread pool will probably be an easy fix. Then the rules we are building are... * If you are going to call a synchronous filesystem method (e.g. Close, DeleteDirContents) then you must be on the CPU thread pool. * If you are a synchronous filesystem method then you are only allowed to spawn one I/O task and wait for it. ...I think that will prevent any sort of nested deadlock. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
