Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8F00217361 for ; Wed, 21 Oct 2015 19:44:50 +0000 (UTC) Received: (qmail 33191 invoked by uid 500); 21 Oct 2015 19:44:50 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 33139 invoked by uid 500); 21 Oct 2015 19:44:49 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 33128 invoked by uid 99); 21 Oct 2015 19:44:49 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Oct 2015 19:44:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3F760C0FAF for ; Wed, 21 Oct 2015 19:44:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.991 X-Spam-Level: ** X-Spam-Status: No, score=2.991 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id U3L9lGvjvXQ4 for ; Wed, 21 Oct 2015 19:44:36 +0000 (UTC) Received: from COL004-OMC3S7.hotmail.com (col004-omc3s7.hotmail.com [65.55.34.145]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 266DC20751 for ; Wed, 21 Oct 2015 19:44:35 +0000 (UTC) Received: from COL128-W54 ([65.55.34.135]) by COL004-OMC3S7.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 21 Oct 2015 12:44:28 -0700 X-TMN: [b7jL6mhEZpZELXviQkkEFYaHocvglTBi] X-Originating-Email: [adrian.hamza@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_e597a160-6ea4-4d2c-9a03-714f199fab6b_" From: Adrian Hamza To: "user@zookeeper.apache.org" Subject: RE: Running zookeeper with journaling disabled on an ext4 Date: Wed, 21 Oct 2015 12:44:28 -0700 Importance: Normal In-Reply-To: References: ,, MIME-Version: 1.0 X-OriginalArrivalTime: 21 Oct 2015 19:44:28.0788 (UTC) FILETIME=[E60EB340:01D10C38] --_e597a160-6ea4-4d2c-9a03-714f199fab6b_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable No fsync can lead to data loss as the data could be written only in the OS = cache but no on the disk. We do use fsync to prevent that and we are not go= ing to disable it. > Date: Wed=2C 21 Oct 2015 14:00:57 -0400 > Subject: Re: Running zookeeper with journaling disabled on an ext4 > From: edward.capriolo@huffingtonpost.com > To: user@zookeeper.apache.org >=20 > There used to be this setting in zk. >=20 > zookeeper.forceSync > Using Kafka I used to set this setting to false=2C The reason is I had a > number of clients writing offsets to zk and the disk system was always > sync-ing dirty pages. The system would be super high IO wait. >=20 > I set this to false and disk usage basically dropped to 0. >=20 > On Wed=2C Oct 21=2C 2015 at 1:47 PM=2C Ivan Kelly wrot= e: >=20 > > > > > > What's your opinion on running Zookeeper with file system journaling > > > disabled on an EXT4 file system? > > > We need every ounce of performance out of it=2C and I believe given t= he > > > Zookeeper implementation (operations are logged=2C majority quorum is > > > required for succeeding=2C checkpoints are swapped only after being > > complete) > > > I feel that EXT4 journaling is redundant. Disabling EXT4 journaling c= ould > > > improve performance. We have 5 servers in a Zookeeper ensemble. Am I > > > missing something or this should be fine? > > > > I would recommend against it. With ext4 journalling disabled=2C a serve= r > > crash will likely lose data=2C unless you have all write caching disabl= ed. If > > you have all write caching disabled=2C I'd expect to see worse performa= nce > > for all applications. It's not much safer than running in a ramdisk. > > > > -Ivan > > = --_e597a160-6ea4-4d2c-9a03-714f199fab6b_--