sumanthssr opened a new issue, #6963:
URL: https://github.com/apache/kyuubi/issues/6963

   ### 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/kyuubi/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Describe the bug
   
   i have set kyuubi.engine.share.level=GROUP and 
kyuubi.session.engine.group.id=org0_group in kyuubi-defaults.conf, i have 
executor=1 set in default conf, but when i fire sql queries via jdbc connection 
i see two different driver pods executors pods coming up i.e 
kyuubi-group-spark-sql-bdpadmin-6175-default-50467738-0cad-48ca-8904-21442317f26a-driver
 and 
kyuubi-group-spark-sql-bdpadmin-6090-default-f56582b7-65d3-444d-8bdc-efa8a076562f-driver
 triggered. Shouldn't it be single driver pod for jdbc calls if i set above 
values?
   
   kyuubi.engine.share.level=GROUP
   kyuubi.session.engine.group.id=org0_group
   kyuubi.session.engine.reuse=true
   
   ### Affects Version(s)
   
   1.8
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Server Configurations
   
   ```yaml
   
   ```
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   
   ```
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi 
community to fix.
   - [ ] No. I cannot submit a PR at this time.


-- 
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