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

   ### 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
   
   On Kubernetes, SparkSQLEngine.generateExecutorPodNamePrefixForK8s builds the 
executor podNamePrefix as kyuubi-<user>-<epoch-millis>. When two engines for 
the same user (same resolvedUserName) are launched within the same millisecond 
in the same namespace — for example, a burst of short-lived engines from the 
same user, or two Kyuubi servers racing to launch engines for the same USER 
share level — the two engines get an identical 
spark.kubernetes.executor.podNamePrefix. Their executor pod names 
(<prefix>-exec-<id>) then collide inside the namespace, and one of the two apps 
fails to create executors until the other releases the names.
   
   ### Affects Version(s)
   
   master
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Server Configurations
   
   ```yaml
   
   ```
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   
   ```
   
   ### Additional context
   
   Reproducible by calling 
SparkSQLEngine.generateExecutorPodNamePrefixForK8s("same_user") in a tight loop 
— many calls land on the same millisecond and produce identical prefixes.
   
   ### Are you willing to submit PR?
   
   - [x] 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