ulysses-you opened a new issue, #2686: URL: https://github.com/apache/incubator-kyuubi/issues/2686
### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) ### Search before asking - [X] I have searched in the [issues](https://github.com/apache/incubator-kyuubi/issues?q=is%3Aissue) and found no similar issues. ### Describe the bug We should not set a timeout for acquiring lock. Let's say we have three clients with same request lock to two kyuubi server instances. client A ---> kyuubi X -- first acquired \ client B ---> kyuubi X -- second acquired -- zookeeper client C ---> kyuubi Y -- third acquired / The first client A acqiured the lock then B and C are blocked until A release the lock, with the A created engine state: - SUCCESS B acquired the lock then get engine ref and release the lock. C acquired the lock then get engine ref and release the lock. - FAILED or TIMEOUT B acquired the lock then try to create engine again. C should be still blocked since B is creating engine, otherwise two engines will be created Also different engine type should use its own lock. ### Affects Version(s) master/1.5 ### Kyuubi Server Log Output _No response_ ### Kyuubi Engine Log Output _No response_ ### Kyuubi Server Configurations _No response_ ### Kyuubi Engine Configurations _No response_ ### Additional context _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! -- 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]
