You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/12/03 22:51:11 UTC
[jira] [Resolved] (ACCUMULO-4069) Services failing to renew
Kerberos ticket
[ https://issues.apache.org/jira/browse/ACCUMULO-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser resolved ACCUMULO-4069.
----------------------------------
Resolution: Fixed
> Services failing to renew Kerberos ticket
> -----------------------------------------
>
> Key: ACCUMULO-4069
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4069
> Project: Accumulo
> Issue Type: Bug
> Components: gc, master, monitor, tserver
> Affects Versions: 1.7.0
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Labels: kerberos
> Fix For: 1.7.1, 1.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Got a report from a user that Accumulo services were dying after a period of time that was suspiciously similar to the Kerberos ticket lifetime.
> A Kerberos ticket lifetime is the amount of time that the ticket is valid (obtained from password or keytab). There is also a renewable lifetime associate with each ticket. Within the renewable lifetime duration, clients can "renew" their ticket for another "ticket lifetime" duration. For each, a lifetime of one day and a renewable lifetime of seven days: a ticket is valid for one day, but clients can renew that ticket up to 6 days after the original ticket expires.
> I do recall seeing a line of code in our services that has a comment saying it should spawn a thread specifically for this purpose, but I don't ever recall seeing that thread in thread dumps. My hunch is that the thread just isn't getting launched and we're not doing renewals
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)