[jira] [Resolved] (IMPALA-4860) Stagger impala TGS_REQ to KDC

["Michael Ho (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Ho resolved IMPALA-4860.
--------------------------------
       Resolution: Duplicate
    Fix Version/s: Not Applicable

> Stagger impala TGS_REQ to KDC
> -----------------------------
>
>                 Key: IMPALA-4860
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4860
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Distributed Exec, Security
>    Affects Versions: Impala 2.6.0, Impala 2.7.0, Impala 2.8.0
>            Reporter: Mala Chikka Kempanna
>            Priority: Major
>              Labels: kerberos, scalability, supportability
>             Fix For: Not Applicable
>
>
> During initial startup when first query is run on cluster or at end of --kerberos_reinit_interval, each impala daemon sends out N-1 number of TGS_REQ to KDC where N is the number of impala daemons. This amounts to N(N-1) TGS_REQ at once going from impala service to KDC.
> This tends to overload KDC server.
> The request here is to stagger these TGS_REQ requests so all of them do not hit KDC at the same time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)