[
https://issues.apache.org/jira/browse/KYLIN-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736640#comment-14736640
]
fengYu commented on KYLIN-1014:
-------------------------------
I actually met the issue of ticket expired while execute a job, But in normal
condition the problem do not the major one if you setup a crontab job update
the ticket. When getting job status from RM we must USE AuthSchemes.SPNEGO even
the client ticket is vaild !
In another project , we can create a thread when starting server. the thread is
in charge of registering and refreshing kerberos ticket every couple hours.
However, we need execute some command by starting a subprocess , I do not know
if it's still valid in subprocess, I will test this ..
By the way, [~sunyerui] I want to know what is your measure to solving the
problem of getting job status from RM. Thanks...
> patch for supporting kerberos authentication while getting status from RM
> -------------------------------------------------------------------------
>
> Key: KYLIN-1014
> URL: https://issues.apache.org/jira/browse/KYLIN-1014
> Project: Kylin
> Issue Type: Bug
> Reporter: fengYu
> Attachments: 0001-kerberos.patch
>
>
> I have used kylin-0.7.2 build cube and do some query, and I am trying
> kylin-1.0 in another hadoop cluster. I get this problem below in kylin-0.7.2
> and kylin-1.0 :
> Our hadoop cluster deals with authentication with kerberos, However, We find
> after submit a mapreduce job(the second step in building cube), kylin will
> send a http request to RM server and get the job status at regular intervals,
> But we always get errors here because kylin do nothing about kerberos.
> Finally , we do some change on source code and make it support kerberos
> authentication . attachment is my patch file..
> I add a property named "kylin.job.status.with.kerberos" which means if we
> need do authentication with kerberos when getting status from RM, the default
> value is false.
> It will be highly appreciated if you have some good idea or some suggestion.
> Thanks...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
