[jira] [Resolved] (IMPALA-1770) Concurrent query right after impala restart can cause connection error in a secure cluster

["Tim Armstrong (Jira)" <ji...@apache.org>]

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

Tim Armstrong resolved IMPALA-1770.
-----------------------------------
    Resolution: Cannot Reproduce

> Concurrent query right after impala restart can cause connection error in a secure cluster
> ------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-1770
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1770
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: Impala 2.1.1
>            Reporter: Henry Robinson
>            Priority: Minor
>              Labels: kerberos, security
>
> Here's the error message:
> {Query Status: Couldn't open transport for c2114.hal.cloudera.com:22000 (SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Cannot contact any KDC for realm 'HAL17.CLOUDERA.COM'))}
> To reproduce it, go to the 17-node (CM = c2102.hal.cloudera.com:7180)
> 1. ssh to c2102.hal.cloudera.com
> 2. sudo su
> 3. run "k5start -f /cdep/keytabs/systest.keytab -K 10 -l 1d -u systest -b"
> 4. cd /home/alan/benchmark
> 5. Restart Impala service in CM
> 6. in the ssh shell, run "../queries/no_group_agg.txt"
> You can then go to the impala debug webpage. The query will stuck at "CREATE" for a while, and then you'll see this error.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)