[HAWQ-1622] Cache PXF proxy UGI so that cleanup of FileSystem cache doesn't have to be done on each request

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.4.0.0
• Component/s: PXF
• Assignee: Lav Jain
• Reporter: Alexander Denissov
• Created: 01/Jun/18 00:10
• Updated: 26/Jul/18 19:14
• Resolved: 26/Jul/18 19:08

Description

Closing PXF proxy UGIs on each request (implemented in HAWQ-1621) slows down PXF request response time significantly when several threads work concurrently as it locks FileSystem cache and holds the lock while the cleanup of DFSClients is completed.

This can be avoided by caching the proxy UGI for a given proxy user between requests. Care must be taken to remove the cached entry after some pre-defined TTL if and only if there are no current threads using any FileSystem entries held by the cache. A combination of TTL-based cache with ref-counting might be utilized to achieve this.

 

For some example of this, see: 

https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/UserGroupInformationService.java

Caching UGIs might be tricky when Kerberos support is implemented later, see: https://issues.apache.org/jira/browse/HIVE-3098?focusedCommentId=13398979&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13398979

Issue Links

• is duplicated by: HAWQ-1635 Cache Hadoop UGI for subsequent requests when PXF impersonation is on
• links to: GitHub Pull Request #1379
• links to: GitHub Pull Request #1379