[
https://issues.apache.org/jira/browse/HADOOP-12876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324265#comment-15324265
]
Steve Loughran commented on HADOOP-12876:
-----------------------------------------
# Would this be per FS instance, or across all instances? Because the latter,
even though nominally more efficient if there is >1 FS against the same URI,
has some security implications on any service fielding requests from >1
principal.
# Guava has a cache with eviction policies; I'd go with that unless it was
fundamentally broken
# Making it generic to filesystems would allow use elsewhere (Swift, S3a), as
well as isolated testing
# would there be cache invalidation after file/directory operations?
> [Azure Data Lake] Support for process level FileStatus cache to optimize
> GetFileStatus frequent opeations
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-12876
> URL: https://issues.apache.org/jira/browse/HADOOP-12876
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs, fs/azure, tools
> Reporter: Vishwajeet Dusane
> Assignee: Vishwajeet Dusane
>
> Add support to cache GetFileStatus and ListStatus response locally for
> limited period of time. Local cache for limited period of time would optimize
> number of calls for GetFileStatus operation.
> One of the example where local limited period cache would be useful -
> terasort ListStatus on input directory follows with GetFileStatus operation
> on each file within directory. For 2048 input files in a directory would save
> 2048 GetFileStatus calls during start up (Using the ListStatus response to
> cache FileStatus instances).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
