qshian opened a new issue, #3403:
URL: https://github.com/apache/incubator-kyuubi/issues/3403

   ### 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
   
   
![image](https://user-images.githubusercontent.com/7300976/188373486-6db352a7-7694-4285-a275-7bdf6b171284.png)
   
   用java jdbc的方式连接 kyuubi ,提交一条sql , spark 会生成两个集群。一个是show databases,另外一个是 show 
databases + 提交的sql 。
   
   
![image](https://user-images.githubusercontent.com/7300976/188373895-c7680129-03e4-4e91-975c-d5d1783e1e22.png)
   
   
   
![image](https://user-images.githubusercontent.com/7300976/188374049-16f21797-2e2b-4139-aaf5-fac1b0b7d7b3.png)
   
   
   这种在connection的模式下, 我的理解,show tables是engine_initializing_queries 
在SparkSqlEngine 135 行执行,后面都是返回这个session ,为什么会产生两个spark 作业了,向k8s申请两次不同的资源了。
   
   ### Affects Version(s)
   
   1.5.1
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   没有报错
   ```
   
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   没有报错
   ```
   
   
   ### Kyuubi Server Configurations
   
   ```yaml
   kyuubi.session.engine.initialize.timeout 600000
       # 约定Driver闲置了多长时间以后也释放
       kyuubi.session.engine.idle.timeout 300000
       kyuubi.engine.share.level CONNECTION
       kyuubi.engine.connection.url.use.hostname false
       kyuubi.session.idle.timeout  1800000
   ```
   
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   没有配置
   ```
   
   
   ### Additional context
   
   无
   
   ### 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]

Reply via email to