hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13649) s3guard: implement time-based (TTL) expiry for LocalMetadataStore
Date Fri, 01 Sep 2017 13:49:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated HADOOP-13649:
    Affects Version/s: 3.0.0-beta1
             Priority: Minor  (was: Major)

> 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: Aaron Fabbri
>            Priority: Minor
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message