baibaichen commented on pull request #34292: URL: https://github.com/apache/spark/pull/34292#issuecomment-944846227
@cloud-fan It is what I talked to you about in the private chat. It looks like Spark assume the lock order is `CalatogManager` => `SessionCatalog`. We implement a new external catalog that could result in reverse order and hence deadlock. To extract `v1SessionCatalog.getCurrentDatabase` from the `CalatogManager`'s synchronized block could avoid deadlock as well as improving scalability. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
