We encountered the same issue in yarn's RM so I made the RM recognize it's own
tokens and renew them regardless of the renewer. In part because older
versions of oozie hardcode the renewer as mrtoken. I thought the change made
it back into 1.x JT but I guess not.
I agree that the conversion
Well, that does not seem to be the issue. The Kerberos ticket gets refreshed
automatically, but the delegation token doesn't.
Le 3 déc. 2013 à 20:24, Raviteja Chirala a écrit :
Alternatively you can schedule a cron job to do kinit every 20 hours or so.
Just to renew token before it expires.
It is clearly mentioning that the renewer is wrong (renewer marked is 'nobody'
but mapred is trying to renew the token), you may want to check this.
Thanks,
+Vinod
On Dec 2, 2013, at 8:25 AM, Rainer Toebbicke wrote:
2013-12-02 15:57:08,541 ERROR
Alternatively you can schedule a cron job to do kinit every 20 hours or so.
Just to renew token before it expires.
—
Sent from Mailbox for iPad
On Mon, Dec 2, 2013 at 9:12 AM, Rainer Toebbicke r...@pclella.cern.ch
wrote:
Hello,
I am trying to understand why my long-running mapreduce jobs
Hello,
I am trying to understand why my long-running mapreduce jobs stop after 24
hours (approx) on a secure cluster.
This is on Cloudera CDH 4.3.0, hence hadoop 2.0.0, using mrv1 (not yarn),
authentication specified as kerberos. Trying with a short-lived Kerberos
ticket (1h) I see that it