accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dlmarion <...@git.apache.org>
Subject [GitHub] accumulo issue #176: Wrote blog post about durability and performance
Date Mon, 31 Oct 2016 13:29:27 GMT
Github user dlmarion commented on the issue:

    https://github.com/apache/accumulo/pull/176
  
    > I'm not sure I understand the reasoning behind that logic (admittedly, it's "early").
Specifically, how would a failure of the local node be any different than a failure of a non-local
DN in the write pipeline?
    
    It might be how we create/use the WAL. It's possible that a tserver can create a WAL and
open an output stream to the first block, but never actually write any data to it (see ACCUMULO-4004).
I'm not quite sure of the state of the first block and file from an HDFS perspective if the
node dies while in this state (WAL created, open input stream to the first block). But, I
can say that this does cause a problem (in Accumulo 1.6.4 at least).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message