You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Aaron Fabbri (JIRA)" <ji...@apache.org> on 2018/07/19 22:23:00 UTC

[jira] [Created] (HADOOP-15621) s3guard: implement time-based (TTL) expiry for DynamoDB Metadata Store

Aaron Fabbri created HADOOP-15621:
-------------------------------------

             Summary: s3guard: implement time-based (TTL) expiry for DynamoDB Metadata Store
                 Key: HADOOP-15621
                 URL: https://issues.apache.org/jira/browse/HADOOP-15621
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
    Affects Versions: 3.0.0-beta1
            Reporter: Aaron Fabbri
            Assignee: Gabor Bota
             Fix For: 3.2.0


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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org