As an aside, while digging around in the code, I noticed that the Atlas
Reporting Task has its own Hadoop Kerberos authentication logic
(org.apache.nifi.atlas.security.Kerberos). I'm not using this, but it made me
wonder if this could cause trouble if Hive (synchronized) and Atlas (separate,
un
If you're using the Hortonworks distribution it's fixed in the latest HDF 3.x
release I think.
Thanks
Shawn
From: Peter Wicks (pwicks)
Sent: Friday, July 27, 2018 10:58 AM
To: users@nifi.apache.org
Subject: RE: [EXT] Re: Hive w/ Kerberos Authentication starts
Thanks Shawn. Looks like this was fixed in 1.7.0. Will have to upgrade.
From: Shawn Weeks [mailto:swe...@weeksconsulting.us]
Sent: Friday, July 27, 2018 8:07 AM
To: users@nifi.apache.org
Subject: Re: [EXT] Re: Hive w/ Kerberos Authentication starts failing after a
week
See NIFI-5134 as there wa
See NIFI-5134 as there was a known bug with the Hive Connection Pool that made
it fail once the Kerberos Tickets expired and you lost your connection from
Hive. If you don't have this patch in your version once the Kerberos Tickets
reaches the end of it's lifetime the connection pool won't work
I don’t believe that is how this code works. Not to say that might not work,
but I don’t believe that the Kerberos authentication used by NiFi processors
relies in any way on the tickets that appear in klist.
While we are only using a single account on this particular server, many of our
server
Why not have the java tmp dir be configurable and make sure this doesn’t
happen for any other possible nar?
It is a more generic solution.
On July 26, 2018 at 17:23:31, Matt Burgess (mattyb...@apache.org) wrote:
This has been biting a few users lately, not sure when it changed
exactly, but the H
Did you try executing 'klist' to see if the tickets are there and renewed?
If expired, try manual kinit and see if that fixes.
On Fri, Jul 27, 2018 at 1:51 AM Peter Wicks (pwicks)
wrote:
> We are seeing frequent failures of our Hive DBCP connections after a week
> of use when using Kerberos with
