accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-2932) Increased control over write durability
Date Wed, 27 Aug 2014 13:21:57 GMT

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

Eric Newton resolved ACCUMULO-2932.
-----------------------------------

    Resolution: Duplicate

> Increased control over write durability
> ---------------------------------------
>
>                 Key: ACCUMULO-2932
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2932
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Josh Elser
>            Assignee: Eric Newton
>
> ACCUMULO-2842 introduced the ability to configure the HDFS method that is use to sync
WALs. This was mainly done as a means to investigate the performance characteristic of hflush
and hsync. As such, it was was trivially done system-wide.
> However, there is also practical application to allowing this configuration, in addition
to some internal concerns.
> # We should *always* sync WALs involved in {{accumulo.metadata}}
> # Data loss may be acceptable on some user tables and not on others (we may want to use
hflush for some tables, hsync for other). The option must have the granularity to specify
at least on the table (if not locality group).
> When multiple tablets are using a WAL with differing durability guarantees, we should
choose the higher durability.
> If we compare this to HBase, we could also implement it on the per Mutation level, however
that's beyond the scope here.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message