Viktor Bogdanov created SPARK-26420:
---------------------------------------
Summary: [kubernetes] driver service id is not random
Key: SPARK-26420
URL: https://issues.apache.org/jira/browse/SPARK-26420
Project: Spark
Issue Type: Improvement
Components: Kubernetes
Affects Versions: 2.3.2
Environment: Spark 2.3.2
Kubernetes 1.10.11
Reporter: Viktor Bogdanov
I faced with a very rare situation
```
2018-12-20 04:34:46 WARN DriverServiceBootstrapStep:66 - Driver's hostname
would preferably be one-job-41944f13918f3d779f7dc8cfea489791-driver-svc, but
this is too long (must be <= 63 characters). Falling back to use
spark-1545280486832-driver-svc as the driver service's name.
2018-12-20 04:34:46 WARN DriverServiceBootstrapStep:66 - Driver's hostname
would preferably be
completely-different-job-017608e0359a3d7389667280f45ec562-driver-svc, but this
is too long (must be <= 63 characters). Falling back to use
spark-1545280486832-driver-svc as the driver service's name.
```
Two different spark-submits chouse the same name for driver service
This happened because service id is chosen by clock.getTimeMillis() function
[code
line|https://github.com/apache/spark/blob/98c0ca78610ccf62784081353584717c62285485/resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/features/DriverServiceFeatureStep.scala#L45]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
