You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/03/12 04:49:00 UTC
[jira] [Resolved] (IMPALA-9359) Recover gracefully from corrupt
kerberos credential cache
[ https://issues.apache.org/jira/browse/IMPALA-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-9359.
-----------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Recover gracefully from corrupt kerberos credential cache
> ---------------------------------------------------------
>
> Key: IMPALA-9359
> URL: https://issues.apache.org/jira/browse/IMPALA-9359
> Project: IMPALA
> Issue Type: Improvement
> Components: Security
> Affects Versions: Impala 3.3.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: kerberos
> Fix For: Impala 3.4.0
>
>
> # Start up a kerberized Impala cluster
> # Corrupt the kerberos ticket cache used by impala /tmp/krb5cc_impala_internal
> # Observe queries fail. The details depend a lot on timing, etc. I have seen communication failures between impalads and with other systems, e.g. HDFS.
> # The system will stay wedge in this state indefinitely
> We have seen this happen once in production from /tmp filling up.
> I prototyped a fix that amounts to re-running Kinit() to blow away the broken credential cache. It needs more work to be production-ready
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org