Github user dbahir commented on the issue:
https://github.com/apache/phoenix/pull/203
Regarding the renewal, I understand from,
http://stackoverflow.com/questions/34616676/should-i-call-ugi-checktgtandreloginfromkeytab-before-every-action-on-hadoop,
that the RPC layer takes care of that.
I am trying to fix the scenario in which multiple threads call
loginUserFromKeytab concurrently and then the renewal process no longer works
as expected.
An example of that scenario is a storm topology that has multiple
HBase/Phoenix/HDFS bolts in the same JVM. When the topology starts it will
initialize all bolts which will execute a login from each one, when that
happens the renewal no longer works. If only one login happens the renewal
works properly.
In regarding to Phoenix, we came got into a similar situation with a
multi-threaded application that caused loginUserFromKeytab to be called
concurrently. The code change was made to protect that and works.
Your concern regarding security is correct.
I looked into PHOENIX-3189 which i was not aware of. The fix can be folded
into it however we would need to handle synchronization of the
loginUserFromKeytab if multple instances of the driver are created.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
