Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2E389EC08 for ; Sat, 9 Mar 2013 18:53:13 +0000 (UTC) Received: (qmail 9747 invoked by uid 500); 9 Mar 2013 18:53:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 9700 invoked by uid 500); 9 Mar 2013 18:53:12 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 9664 invoked by uid 99); 9 Mar 2013 18:53:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Mar 2013 18:53:12 +0000 Date: Sat, 9 Mar 2013 18:53:12 +0000 (UTC) From: "Eric Newton (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1083) add concurrency to HDFS write-ahead log MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598037#comment-13598037 ] Eric Newton commented on ACCUMULO-1083: --------------------------------------- bq. Does each datanode writing a replica need to complete the write before the TServer will return to the client? Yes, in the normal case. However multiple sync's and replications can run in parallel on the same file. > add concurrency to HDFS write-ahead log > --------------------------------------- > > Key: ACCUMULO-1083 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1083 > Project: Accumulo > Issue Type: Improvement > Components: tserver > Reporter: Adam Fuchs > Fix For: 1.6.0 > > Attachments: walog-performance.jpg, walog-replication-factor-performance.jpg > > > When running tablet servers on beefy nodes (lots of disks), the write-ahead log can be a serious bottleneck. Today we ran a continuous ingest test of 1.5-SNAPSHOT on an 8-node (plus a master node) cluster in which the nodes had 32 cores and 15 drives each. Running with write-ahead log off resulted in a >4x performance improvement sustained over a long period. > I believe the culprit is that the WAL is only using one file at a time per tablet server, which means HDFS is only appending to one drive (plus replicas). If we increase the number of concurrent WAL files supported on a tablet server we could probably drastically improve the performance on systems with many disks. As it stands, I believe Accumulo is significantly more optimized for a larger number of smaller nodes (3-4 drives). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira