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 43D25200C87 for ; Wed, 17 May 2017 08:25:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4233A160BBA; Wed, 17 May 2017 06:25:20 +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 60AFD160BB5 for ; Wed, 17 May 2017 08:25:19 +0200 (CEST) Received: (qmail 62213 invoked by uid 500); 17 May 2017 06:25:18 -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 62201 invoked by uid 99); 17 May 2017 06:25:17 -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; Wed, 17 May 2017 06:25:17 +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 5ADD1180A5A for ; Wed, 17 May 2017 06:25:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.48 X-Spam-Level: ** X-Spam-Status: No, score=2.48 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=motum-be.20150623.gappssmtp.com 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 fti0-ca-lG51 for ; Wed, 17 May 2017 06:25:15 +0000 (UTC) Received: from mail-vk0-f50.google.com (mail-vk0-f50.google.com [209.85.213.50]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 967C75F567 for ; Wed, 17 May 2017 06:25:14 +0000 (UTC) Received: by mail-vk0-f50.google.com with SMTP id y190so1504007vkc.1 for ; Tue, 16 May 2017 23:25:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=motum-be.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ej9D+JL2y0KP69QBh77G0NtdJ3XerkTUS9XDEbZSJho=; b=ExyVdRLDzjYrKdtmZPwd6JclAN8CJpTmVqdeCOSZHiUcJrxy2Y8Vgh0rUNtQ0nxhG9 vJLRrxrwNkgcQQnu8qqvZwbMTue6yVb2xpIGJSPPN0o4UL/WOO/haBjuxYGOPUZlXexr OsJRVABb8kj+c9FOCjI6EzFlIFm8X5DqUD1gUIO5+VnJ5TUMWDv+l9Mpm7Dpl/u4mPGP tMyns6zDKbVc+GFZxmghfKSh2xTusOcBT7dFI4U/w494Uz2XLR3yLbqiCwdP6sq+Aasd 5ewkraaqvIcn3LUsvOuZEOOeP+R7W/MLROcpon4ib0GFwe5B61X9Wor/01NgK7HNjnvF OvUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ej9D+JL2y0KP69QBh77G0NtdJ3XerkTUS9XDEbZSJho=; b=tdZDx7GF5rYpVv1bv39EBO+ctRCGpRnQZVxSXkY+2FH+b65DdHGUrC2zz5VddFGsEc cfVwTaUHfflJdPbK2l1pa8jdleiiIcUbrWsahPFq053R0FeYOJcQKW994HSHoJ5ghdxr 7J8IJIbDVZxt7zw/nReKJ+NSVRKRaimFb0/YixShyordzUM7fU/agg8qfKHa7yxboLS+ tXGGvh0dqeQLzI9WX5IaCBFwxvsl1vAyq4fsLMjS0qwYz9r34ORm+HNppI/CYESn72ID r7xHlXfSt/eWrvbr0T3fS/YeX2w/TuIftWqDYBg8+EVYGk1gt3M1n8zhL67X4ir1vrd7 Dtaw== X-Gm-Message-State: AODbwcDU0flPI7XnxV4UM3eZC31jl13iCGaqmboNIq0s17SQSlkm8nxQ KDiNnbogCogo9Gzb4Gn4EZgP6BglZTt0 X-Received: by 10.31.106.5 with SMTP id f5mr205063vkc.69.1495002313307; Tue, 16 May 2017 23:25:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.50.135 with HTTP; Tue, 16 May 2017 23:25:12 -0700 (PDT) In-Reply-To: References: From: Mike Richardson Date: Wed, 17 May 2017 08:25:12 +0200 Message-ID: Subject: Re: Observers taking long time to serve requests To: user@zookeeper.apache.org Content-Type: multipart/related; boundary="94eb2c093de4d39fe9054fb259c2" archived-at: Wed, 17 May 2017 06:25:20 -0000 --94eb2c093de4d39fe9054fb259c2 Content-Type: multipart/alternative; boundary="94eb2c093de4d39fe5054fb259c1" --94eb2c093de4d39fe5054fb259c1 Content-Type: text/plain; charset="UTF-8" Unsubscribe Mike Richardson Senior Software Engineer *MoTuM N.V. | Dellingstraat 34 | B-2800 MECHELEN | Belgium* T +32(0)15 28 16 63 M +41 7943 69538 www.motum.be On 16 May 2017 at 23:07, Michael Han wrote: > When an observer (and in general a follower) restarted, it will go through > these stages: > > * Look for leader by starting a new leader election round and usually this > is quick as there is already a leader. > * Register with leader and begin synchronize phase - depends on the > observer state the sync might end up with DIFF (quicker) or SNAPSHOT > (longer). > * After sync phase observer will start serving traffic. > > Check the observer server log and record how long it took for each stage is > a good starting point.. > > > On Tue, May 16, 2017 at 1:04 PM, Ben Sherman wrote: > > > With latency that high, I'd expect the thruput to be low, is 30m in line > > with what it takes to transfer a gig of data across that pipe? > > > > On Mon, May 15, 2017 at 4:19 PM, rammohan ganapavarapu < > > rammohanganap@gmail.com> wrote: > > > > > Hi, > > > > > > We have a zookeeper cluster in multi region, we have leader in US EAST > > and > > > observers in US WEST, our data size is 1.3GB,network latency between > > leader > > > and observers is around 250ms, upon observer restart it is taking like > > > close to 30m for observer to serve traffic. Not sure why it's taking so > > > long to serve request. Does any one see such issue? any idea why it's > > > taking time? > > > > > > Thanks, > > > Ram > > > > > > > > > -- > Cheers > Michael. > --94eb2c093de4d39fe5054fb259c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Unsubscribe

=
Mike Richardson

=
Senior Software Engineer



MoTuM N.V. | De= llingstraat 34 | B-2800 MECHELEN | Belgium


T +32(0)15 28 16 63
M +41 7943 69538=

www.motum.be

On 16 May 2017 at 23:07, Michael Han <hanm@= cloudera.com> wrote:
When a= n observer (and in general a follower) restarted, it will go through
these stages:

* Look for leader by starting a new leader election round and usually this<= br> is quick as there is already a leader.
* Register with leader and begin synchronize phase - depends on the
observer state the sync might end up with DIFF (quicker) or SNAPSHOT
(longer).
* After sync phase observer will start serving traffic.

Check the observer server log and record how long it took for each stage is=
a good starting point..


On Tue, May 16, 2017 at 1:04 PM, Ben Sherman <bensherman@gmail.com> wrote:

> With latency that high, I'd expect the thruput to be low, is 30m i= n line
> with what it takes to transfer a gig of data across that pipe?
>
> On Mon, May 15, 2017 at 4:19 PM, rammohan ganapavarapu <
> rammohanganap@gmail.com= > wrote:
>
> > Hi,
> >
> > We have a zookeeper cluster in multi region, we have leader in US= EAST
> and
> > observers in US WEST, our data size is 1.3GB,network latency betw= een
> leader
> > and observers is around 250ms, upon observer restart it is taking= like
> > close to 30m for observer to serve traffic. Not sure why it's= taking so
> > long to serve request. Does any one see such issue? any idea why = it's
> > taking time?
> >
> > Thanks,
> > Ram
> >
>



--
Cheers
Michael.

--94eb2c093de4d39fe5054fb259c1-- --94eb2c093de4d39fe9054fb259c2--