Return-Path: X-Original-To: apmail-couchdb-replication-archive@minotaur.apache.org Delivered-To: apmail-couchdb-replication-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0579411A8B for ; Sun, 13 Apr 2014 15:21:25 +0000 (UTC) Received: (qmail 37506 invoked by uid 500); 13 Apr 2014 15:21:24 -0000 Delivered-To: apmail-couchdb-replication-archive@couchdb.apache.org Received: (qmail 36677 invoked by uid 500); 13 Apr 2014 15:21:10 -0000 Mailing-List: contact replication-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: replication@couchdb.apache.org Delivered-To: mailing list replication@couchdb.apache.org Received: (qmail 36656 invoked by uid 99); 13 Apr 2014 15:21:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Apr 2014 15:21:06 +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: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.220.173] (HELO mail-vc0-f173.google.com) (209.85.220.173) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Apr 2014 15:21:01 +0000 Received: by mail-vc0-f173.google.com with SMTP id il7so6439149vcb.18 for ; Sun, 13 Apr 2014 08:20:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=aWK5rUbDUFpo++6zW5DI7y3eNxT695lGFdU8TTiHWgo=; b=OnHtXgRjll25bmFgtppOgRWEps7+Iw0+Ts80pkcXKxwvNgK87sRthu3caZ2JyPq+SL 0eWhVqlK/ExddAkbudeH3V2OlgfHMyKiOyzYFqPUnfYHOuqCXBOvxLDvbFdj6r4KAtmB BnRKLR+CKNJb3R2tkX3EdZ0/Uhx/JErFwzWH9SDc7BOZZg+w4ofjM04zf9en1R1yJkm5 esrEZljrOdO3uS4hHVK2Ym6YZTO540yvd3VQ9GCIJvoeqerPDQh7NJLgLC2TFLtdzG3R 5LJwQ9cdXM3N5S5frmM7YHowaE3HJ/YTHYeZ5+XH38RTxQTjtmSTHAsEQPeqYdf5eLDx iz9Q== X-Gm-Message-State: ALoCoQlbcgD3IpGB4dw1d9YpqZo8wbV8d21zuk9rgbUopgzlHaGsHG0eHDcgRj+WMAQhRJCSC+GT MIME-Version: 1.0 X-Received: by 10.58.107.65 with SMTP id ha1mr32250476veb.1.1397402437950; Sun, 13 Apr 2014 08:20:37 -0700 (PDT) Received: by 10.58.12.169 with HTTP; Sun, 13 Apr 2014 08:20:37 -0700 (PDT) Date: Sun, 13 Apr 2014 16:20:37 +0100 Message-ID: Subject: Checkpointing on read only databases From: Dale Harvey To: replication@couchdb.apache.org Content-Type: multipart/alternative; boundary=089e01229dfeec65ba04f6ee1b6e X-Virus-Checked: Checked by ClamAV on apache.org --089e01229dfeec65ba04f6ee1b6e Content-Type: text/plain; charset=ISO-8859-1 So with checkpointing we write the checkpoint to both A and B and verify they match before using the checkpoint What happens if the src of the replication is read only? As far as I can tell couch will just checkout a checkpoint_commit_error and carry on from the start, The only improvement I can think of is the user specifies they know the src is read only and to only use the target checkpoint, we can 'possibly' make that happen automatically if the src specifically fails the write due to permissions. --089e01229dfeec65ba04f6ee1b6e--