[
https://issues.apache.org/jira/browse/HADOOP-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468074#comment-16468074
]
Hudson commented on HADOOP-13649:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14144 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14144/])
HADOOP-13649 s3guard: implement time-based (TTL) expiry for (fabbri: rev
69aac696d9d4e32a55ba9b6992f41a9ad13424f1)
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/LocalMetadataStore.java
* (edit)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/TestLocalMetadataStore.java
* (delete)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/LruHashMap.java
> s3guard: implement time-based (TTL) expiry for LocalMetadataStore
> -----------------------------------------------------------------
>
> Key: HADOOP-13649
> URL: https://issues.apache.org/jira/browse/HADOOP-13649
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Aaron Fabbri
> Assignee: Gabor Bota
> Priority: Minor
> Fix For: 3.2.0
>
> Attachments: HADOOP-13649.001.patch, HADOOP-13649.002.patch,
> HADOOP-13649.003.patch
>
>
> LocalMetadataStore is primarily a reference implementation for testing. It
> may be useful in narrow circumstances where the workload can tolerate
> short-term lack of inter-node consistency: Being in-memory, one JVM/node's
> LocalMetadataStore will not see another node's changes to the underlying
> filesystem.
> To put a bound on the time during which this inconsistency may occur, we
> should implement time-based (a.k.a. Time To Live / TTL) expiration for
> LocalMetadataStore
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
