Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: joshelser <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-176-accumulo@git.apache.org>
In-Reply-To: <git-pr-176-accumulo@git.apache.org>
Subject: [GitHub] accumulo pull request #176: Wrote blog post about durability and performance
Content-Type: text/plain
Message-Id: <20161031143617.EFFBEE1075@git1-us-west.apache.org>
Date: Mon, 31 Oct 2016 14:36:17 +0000 (UTC)
archived-at: Mon, 31 Oct 2016 14:36:19 -0000

Github user joshelser commented on a diff in the pull request:

    https://github.com/apache/accumulo/pull/176#discussion_r85750520
  
    --- Diff: _posts/blog/2016-10-28-durability-performance.md ---
    @@ -0,0 +1,136 @@
    +---
    +title: "Durability Performance Implications"
    +date: 2016-10-28 17:00:00 +0000
    +author: Keith Turner
    +---
    +
    +## Overview
    +
    +Accumulo stores recently written data in a sorted in memory map.  Before data is
    +added to this map, it's written to an unsorted WAL (write ahead log).  In the
    +case when a Tablet Server dies, the recently written data is recovered from the
    +WAL.
    +
    +When data is written to Accumulo the following happens :
    +
    + * Client sends a batch of mutations to a tablet server
    + * Tablet server does the following :
    +   * Writes mutation to Tablet Servers WAL
    +   * Sync or flush WAL
    +   * Adds mutations to sorted in memory maps
    --- End diff --
    
    My apologies! Ignore this one then.


---
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.
---