[
https://issues.apache.org/jira/browse/HADOOP-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517179#comment-15517179
]
Chris Douglas commented on HADOOP-13452:
----------------------------------------
The {{FileStatusCacheManager}} in HADOOP-12666 also expired its entries after
some configurable duration. In testing, access patterns of many Hadoop
applications benefited from surprisingly low timeouts. Are cache entries
expired at a higher level in the {{MetadataStore}}, or are they evergreen in
this design?
As [~fabbri] suggested in HADOOP-12876, we should unify these, if possible.
Ping [~vishwajeet.dusane]
> S3Guard: Implement access policy for intra-client consistency with in-memory
> metadata store.
> --------------------------------------------------------------------------------------------
>
> Key: HADOOP-13452
> URL: https://issues.apache.org/jira/browse/HADOOP-13452
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Aaron Fabbri
> Attachments: HADOOP-13452-HADOOP-13345.002.patch,
> HADOOP-13452.001.patch
>
>
> Implement an S3A access policy based on an in-memory metadata store. This
> can provide consistency within the same client without needing to integrate
> with an external system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
