Skip to main content
VijaySankar
VijaySankar
Silver ⭐️⭐️
January 20, 2020
Solved

Nifi - SelectHive3QL processor is throwing a Kerberos authentication exception

I am using SelectHive3QL processor in my Nifi flow and it is throwing a below Kerberos authentication exception. Initially it is working fine for some time and after some Idle time, getting a below error. My requirement is "SelectHive3QL" should always up and running without any issues.

 

Exception:

SelectHive3QL[id=47753131-0b9a-39c4-b0e7-2a92ac1042c6] Issue processing SQL select * from egress_test where service_name = 'NDC' due to java.sql.SQLException: Could not open client transport for any of the Server URI's in ZooKeeper: GSS initiate failed.: org.apache.nifi.processor.exception.ProcessException: java.sql.SQLException: Could not open client transport for any of the Server URI's in ZooKeeper: GSS initiate failed

 

Cc: @MattWho , @arunak , @stevenmatison 

MattWho
MattWhoAnswer
Titanium ⭐️⭐️⭐️
January 23, 2020

@VijaySankar 

 

So, it is very likely you are hitting that bug.  If you have a support subscription with Cloudera, you can open a support ticket for a patched release of HDF 3.2.x based off Apache NiFi 1.7.  

If not, your best bet is to upgrade to NiFi 1.10.

Thanks,

Matt

Please take a moment to accept any answers which answered/resolved your query.

View in thread

5 replies

DennisJaheruddi
Platinum ⭐️
DennisJaheruddi
Platinum ⭐️
January 20, 2020

Are you running a recent version of HDF?

This thread suggests it may be an issue that has been resolved: http://apache-nifi.1125220.n5.nabble.com/Hive-w-Kerberos-Authentication-starts-failing-after-a-week-td23887.html

Translate
- Dennis Jaheruddin If this answer helped, please mark it as 'solved' and/or if it is valuable for future readers please apply 'kudos'.
MattWho
Titanium ⭐️⭐️⭐️
MattWho
Titanium ⭐️⭐️⭐️
January 22, 2020

@VijaySankar 

 

What version of NiFi are your running?

It is extremely likely you have encountered following bug:
https://issues.apache.org/jira/browse/NIFI-6210

So if you are not running Apache NiFi 1.10 or newer, you are exposed to this bug specifically affecting the Hive 3 NiFi components.

 

Hope this helps,
Matt

Translate
    VijaySankar
    VijaySankarAuthor
    Silver ⭐️⭐️
    January 23, 2020

    @MattWho Thanks for your response.

     

    Our Nifi version is 1.7.

    Translate
    MattWho
    Titanium ⭐️⭐️⭐️
    MattWhoAnswer
    Titanium ⭐️⭐️⭐️
    January 23, 2020

    @VijaySankar 

     

    So, it is very likely you are hitting that bug.  If you have a support subscription with Cloudera, you can open a support ticket for a patched release of HDF 3.2.x based off Apache NiFi 1.7.  

    If not, your best bet is to upgrade to NiFi 1.10.

    Thanks,

    Matt

    Please take a moment to accept any answers which answered/resolved your query.

    Translate
    Terms & ConditionsAccessibility statement