Kerberos exception: "Failed to find any Kerberos tgt" when creating a session

Livy isn't able to authenticate to RM at times between two kinit calls which refreshes the livy service principal ticket cache. The specific stacktrace is attached as stacktrace.txt.

I also attached whole application stacktrace as opensource-stacktrace.out, where kinit happens at 17/08/04 09:59:09 which updates the ticket cache in /tmp. It happened that all the session creation requests give the TGT not found exception until the next kinit occurred which happened at 17/08/04 10:59:09

Is there a reason why Livy isn't able to use the TGT during this period? Does, using UGI methods avoid this exception? Does it happen when too many context not found exceptions happen?