LucaCanali commented on a change in pull request #23518: [SPARK-26600] Update 
spark-submit usage message
URL: https://github.com/apache/spark/pull/23518#discussion_r247361319
 
 

 ##########
 File path: 
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala
 ##########
 @@ -576,27 +576,26 @@ private[deploy] class SparkSubmitArguments(args: 
Seq[String], env: Map[String, S
         |  --kill SUBMISSION_ID        If given, kills the driver specified.
         |  --status SUBMISSION_ID      If given, requests the status of the 
driver specified.
         |
-        | Spark standalone and Mesos only:
+        | Spark standalone, Mesos and K8S only:
         |  --total-executor-cores NUM  Total cores for all executors.
         |
-        | Spark standalone and YARN only:
-        |  --executor-cores NUM        Number of cores per executor. (Default: 
1 in YARN mode,
-        |                              or all available cores on the worker in 
standalone mode)
+        | Spark standalone, YARN and K8S only:
+        |  --executor-cores NUM        Number of cores used by each executor. 
(Default: 1 in
+        |                              YARN and K8S modes, or all available 
cores on the worker
+        |                              in standalone mode).
         |
-        | YARN-only:
+        | Spark on YARN and K8S only:
+        |  --principal PRINCIPAL       Principal to be used to login to KDC.
+        |  --keytab KEYTAB             The full path to the file that contains 
the keytab for the
+        |                              principal specified above.
 
 Review comment:
   Thanks for reviewing. The text that I cut is mostly about the implementation 
of --keytab (i.e. spark.kerberos.keytab) and refers to the YARN implementation. 
In K8S the implementation is different. Also on YARN this has evolved recently 
BTW. I think it is safe and shorter just to omit the implementation details in 
this scope.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to