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 2CE1A200D0D for ; Fri, 25 Aug 2017 21:44:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2B70516D207; Fri, 25 Aug 2017 19:44: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 7479716D206 for ; Fri, 25 Aug 2017 21:44:06 +0200 (CEST) Received: (qmail 88140 invoked by uid 500); 25 Aug 2017 19:44:04 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 88001 invoked by uid 99); 25 Aug 2017 19:44:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Aug 2017 19:44:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 48432C412E for ; Fri, 25 Aug 2017 19:44:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id i4VSP2w-KfL4 for ; Fri, 25 Aug 2017 19:44:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1C5AA5F238 for ; Fri, 25 Aug 2017 19:44:03 +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 B7930E0C1D for ; Fri, 25 Aug 2017 19:44: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 964A82537E for ; Fri, 25 Aug 2017 19:44:01 +0000 (UTC) Date: Fri, 25 Aug 2017 19:44:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ZOOKEEPER-2349) Update documentation for snapCount MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 25 Aug 2017 19:44:07 -0000 [ https://issues.apache.org/jira/browse/ZOOKEEPER-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142090#comment-16142090 ] ASF GitHub Bot commented on ZOOKEEPER-2349: ------------------------------------------- Github user afine commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/349#discussion_r135338802 --- Diff: src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml --- @@ -823,10 +823,10 @@ server.3=zoo3:2888:3888 role="bold">zookeeper.snapCount) ZooKeeper logs transactions to a transaction - log. After snapCount transactions are written to a log - file a snapshot is started and a new transaction log - file is created. The default snapCount is - 100,000. + log. After the count of transactions which are written to a log + file exceed a runtime-set limit in [snapCount/2, snapCount),a snapshot --- End diff -- I think this is an excellent documentation improvement, but we still may be able to phrase this in a clearer way. It may be good to reiterate that ZooKeeper writes to a transaction log between snapshotting here, so the reader understands the purpose of the snapCount. Perhaps something like: > ZooKeeper records its transactions using snapshots and a transaction log (think write-ahead log). The number of transactions recorded in the transaction log before a snapshot can be taken (and the transaction log rolled) is determined by snapCount. In order to prevent all of the machines in the quorum from taking a snapshot at the same time, each ZooKeeper server will take a snapshot when the number of transactions in the transaction log reaches a runtime generated random value in the [snapCount/2, snapCount) range. > Update documentation for snapCount > ---------------------------------- > > Key: ZOOKEEPER-2349 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2349 > Project: ZooKeeper > Issue Type: Bug > Components: documentation > Reporter: Raghavendra Prabhu > Priority: Minor > Attachments: ZOOKEEPER-2349.patch > > > The documentation states that > {code} > ZooKeeper logs transactions to a transaction > log. After snapCount transactions are written to a log > file a snapshot is started and a new transaction log > file is created. The default snapCount is > 100,000. > {code} > However, in implementation, snapshotting is done when logCount is somwhere in (snapCount/2, snapCount+1], based on the limit set at runtime: > {code} > if (logCount > (snapCount / 2 + randRoll)) { > {code} > as in > https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/server/SyncRequestProcessor.java#L124 -- This message was sent by Atlassian JIRA (v6.4.14#64029)