Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-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 D9E411072C for ; Thu, 29 Aug 2013 13:23:45 +0000 (UTC) Received: (qmail 11079 invoked by uid 500); 29 Aug 2013 13:23:43 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 10938 invoked by uid 500); 29 Aug 2013 13:23:43 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 10930 invoked by uid 99); 29 Aug 2013 13:23:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Aug 2013 13:23:42 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andrey.kouprianov@gmail.com designates 209.85.128.176 as permitted sender) Received: from [209.85.128.176] (HELO mail-ve0-f176.google.com) (209.85.128.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Aug 2013 13:23:35 +0000 Received: by mail-ve0-f176.google.com with SMTP id b10so298659vea.7 for ; Thu, 29 Aug 2013 06:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=3mQRh9QzTfa9ACVFqDBUzAqgiQnt5XMI1UPA6anrpBw=; b=b02p71a5GuMmmnFhdC5fhM+Dz3RJLFlxwmLHw1Ah8/5W2Oy8Av5PoY7cSP+yttM5pN KXe8Pm1s84e6M7D5MhHdsulvxDAPSW6gKFduZTZDMzrofFk4hdQdJoRm+AG4r5w4btGt FUrCORVkG5y/X0HIyQoxX7aEWXRKcjkCZBwT7MWxqKQyhS7J8soXDpp7NeesKrpoZU01 JnKd/Jc45vwQABTL9PeY//TmiuD3mkZirZqF1yPh5TeErn+aaXUTjFgGV63GW8E8Blmr Kb7pZat1BG5L/WxR5VX8kGmq0m+CIKzXJCOGSekrILyh9SWgSLw97BJnxLxniBcnJWb8 r6ow== X-Received: by 10.58.106.82 with SMTP id gs18mr3174954veb.18.1377782595211; Thu, 29 Aug 2013 06:23:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.59.4.42 with HTTP; Thu, 29 Aug 2013 06:22:54 -0700 (PDT) In-Reply-To: References: From: Andrey Kuprianov Date: Thu, 29 Aug 2013 20:22:54 +0700 Message-ID: Subject: Re: Replication percentages on status screen To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=047d7b6d88c82a5a3004e5160275 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6d88c82a5a3004e5160275 Content-Type: text/plain; charset=ISO-8859-1 Disregard that, please. The replication got actually stuck. I had to explicitly stop and then start it over. What we do is we have a script that is executed by a cron job. The script has a few curl commands telling local couch to start pulling from remote servers. Used to work well on 1.1.1, but with 1.3.1 it seems to get stuck. Is there a better way to ensure that replication doesnt stop like that? Andrey On Thu, Aug 29, 2013 at 8:14 PM, Andrey Kuprianov < andrey.kouprianov@gmail.com> wrote: > Hi guys, > > I'm running a few pull replications and basically this is a mesh between 4 > servers (all of them are couch 1.3.1). Some of the replication statuses are > showing 100% progress but some seem to have stuck on a percentage below > 100. Like the one below: > > *Checkpointed source sequence 582782, current source sequence 626908, > progress 92% > ** > ** > * > > > * > * > I have checked replication by trying to save a document on one side and > checking it on the other and it works fine. Is status update showing wrong > values then or is there something else? > > Andrey > --047d7b6d88c82a5a3004e5160275--