[
https://issues.apache.org/jira/browse/HDFS-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423295#comment-13423295
]
Alejandro Abdelnur commented on HDFS-3513:
------------------------------------------
HttpFS uses tomcat which by default has keep-alive ON. but still, the only diff
in my testing is enabling/disabling the FS caching. Regarding your suggestion
of using the same UGi for pipelined request, this is not possible as in
servlets you don't know you are being in a pipelined request and it would mean
we would have to keep UGIs sitting around in HttpFS in a cache. I don't see the
value added of that, plus if a the HttpFS client is doing different doAs, the
same UGI won't work. Because of that, I think the current approach is more
suited and simpler.
> HttpFS should cache filesystems
> -------------------------------
>
> Key: HDFS-3513
> URL: https://issues.apache.org/jira/browse/HDFS-3513
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.0.0-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: HDFS-3513.patch, HDFS-3513.patch, HDFS-3513.patch,
> HDFS-3513.patch
>
>
> HttpFS opens and closes a FileSystem instance against the backend filesystem
> (typically HDFS) on every request. The FileSystem caching is not used as it
> does not have expiration/timeout and filesystem instances in there live
> forever, for long running services like HttpFS this is not a good thing as it
> would keep connections open to the NN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
