Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 5 Nov 2014 23:20:37 +0000 (UTC)
From: "Adam Fuchs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12753219.1415229633000.429027.1415229637187@Atlassian.JIRA>
In-Reply-To: <JIRA.12753219.1415229633000@Atlassian.JIRA>
References: <JIRA.12753219.1415229633000@Atlassian.JIRA>
 <JIRA.12753219.1415229633994@arcas>
Subject: [jira] [Created] (ACCUMULO-3303) funky performance with large WAL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Adam Fuchs created ACCUMULO-3303:
------------------------------------

             Summary: funky performance with large WAL
                 Key: ACCUMULO-3303
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3303
             Project: Accumulo
          Issue Type: Bug
          Components: logger, tserver
    Affects Versions: 1.6.1
            Reporter: Adam Fuchs


The tserver seems to get into a funky state when writing to a large write-ahead log. I ran some continuous ingest tests varying tserver.walog.max.size in {512M, 1G, 2G, 4G, 8G} and got some results that I have yet to understand. I was expecting to see the effects of walog metadata management as described in ACCUMULO-2889, but I also found an additional behavior of ingest slowing down for long periods when using a large walog size.

The cluster configuration was as follows:
{code}
Accumulo version: 1.6.2-SNAPSHOT (current head of origin/1.6)
Nodes: 4
Masters: 1
Slaves: 3
Cores per node: 24
Drives per node: 8x1TB data + 2 raided system
Memory per node: 64GB
tserver.memory.maps.max=2G
table.file.compress.type=snappy (for ci table only)
tserver.mutation.queue.max=16M
tserver.wal.sync.method=hflush
Native maps enabled
{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)