[
https://issues.apache.org/jira/browse/HDFS-16045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352527#comment-17352527
]
Xiaoqiao He commented on HDFS-16045:
------------------------------------
Thanks [~zhuxiangyi] raise this issue here. I think it could be not enough to
use username only to index the FileSystem instance. Consider different
principles but same username then it will index the same FileSystem instance
without any difference when request to Server. But the UGI for FileSystem
instances should be not same for different User actually, this could be common
case for presto especially. Not think deeply, any discussion will welcome.
Thanks again.
> FileSystem.CACHE memory leak
> ----------------------------
>
> Key: HDFS-16045
> URL: https://issues.apache.org/jira/browse/HDFS-16045
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.4.0
> Reporter: Xiangyi Zhu
> Priority: Major
>
> {code:java}
> FileSystem get(final URI uri, final Configuration conf,
> final String user){code}
> When the client turns on the cache and uses the above API to specify the user
> to create a Filesystem instance, the cache will be invalid.
> The specified user creates a new UGI every time he creates a Filesystem
> instance, and cache compares it according to UGI.
> {code:java}
> public int hashCode() {
> return (scheme + authority).hashCode() + ugi.hashCode() + (int)unique;
> }{code}
> Whether you can use username to replace UGI to make a comparison, and whether
> there are other risks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
