[
https://issues.apache.org/jira/browse/SPARK-24270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-24270.
------------------------------------
Resolution: Information Provided
Please use the project's mailing lists for questions. Moreover, since your
question is somewhat specific to Cloudera, I suggest looking at Cloudera's
forums first.
> How to submit spark jobs with kinit sessions without keytab onto a Kerberized
> cluster managed by Cloudera
> ----------------------------------------------------------------------------------------------------------
>
> Key: SPARK-24270
> URL: https://issues.apache.org/jira/browse/SPARK-24270
> Project: Spark
> Issue Type: Question
> Components: Documentation
> Affects Versions: 2.2.1
> Reporter: Ankita
> Priority: Major
>
> Hi,
> We have a cluster that is secured over Kerberos on Cloudera. However, Spark
> is not managed by cloudera. We have our own distribution package with
> packages and deploys Spark 2.21 onto the cluster. The reason being, the
> version of Cloudera is 5.4 which does not support the Spark 2+
> I see that we are able to submit jobs on the cluster with a valid keytab file
> and principal account, but unable to just do kinit and use the ticket
> generated in the session to authenticate the job.
> Is there a way to not use the keytab/prinicipal to be passed explicitly and
> just use the kinit session of the user submitting the job?
> Why is it essential to have a specific keytab file and pass it as args to
> spark submit / spark shell?
> Please provide some context around how Spark authenticates using this data
> and why cant it use Kinit in this case?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
