Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BC414200D4A for ; Tue, 28 Nov 2017 16:20:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BAB07160C01; Tue, 28 Nov 2017 15:20:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0C5AF160C07 for ; Tue, 28 Nov 2017 16:20:06 +0100 (CET) Received: (qmail 5791 invoked by uid 500); 28 Nov 2017 15:20:05 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 5578 invoked by uid 99); 28 Nov 2017 15:20:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2017 15:20:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A92A41806B0 for ; Tue, 28 Nov 2017 15:20:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Yg0BgdDiAi3g for ; Tue, 28 Nov 2017 15:20:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8A9175F576 for ; Tue, 28 Nov 2017 15:20:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 603B2E0F7D for ; Tue, 28 Nov 2017 15:20:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 05955241C3 for ; Tue, 28 Nov 2017 15:20:01 +0000 (UTC) Date: Tue, 28 Nov 2017 15:20:01 +0000 (UTC) From: "Elek, Marton (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-12864) Ozone: Turn off full synced write in RocksDB MetadataStore MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Nov 2017 15:20:07 -0000 Elek, Marton created HDFS-12864: ----------------------------------- Summary: Ozone: Turn off full synced write in RocksDB MetadataStore Key: HDFS-12864 URL: https://issues.apache.org/jira/browse/HDFS-12864 Project: Hadoop HDFS Issue Type: Sub-task Components: ozone Reporter: Elek, Marton Assignee: Elek, Marton Based on the suggestion from [~xyao] I created the patch to turn off fully synced write in the rocksdb. With this patch we measured about 10x performance gain (200 nodes cluster + 30 corona instance). 1. We don't need fully synced rocksdb writing, as HA will cover the few cases when a node would be lost 2. Long term (IMHO) we need to add a possibility to configure any settings in rocksdb, so it could be turned off, but the setSync(false) is a reasonable default. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org