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 851B410931 for ; Tue, 18 Mar 2014 18:04:01 +0000 (UTC) Received: (qmail 62263 invoked by uid 500); 18 Mar 2014 18:03:59 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 62204 invoked by uid 500); 18 Mar 2014 18:03:57 -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 62191 invoked by uid 99); 18 Mar 2014 18:03:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 18:03:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ryan@kumu.io designates 209.85.219.54 as permitted sender) Received: from [209.85.219.54] (HELO mail-oa0-f54.google.com) (209.85.219.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 18:03:50 +0000 Received: by mail-oa0-f54.google.com with SMTP id n16so7469523oag.27 for ; Tue, 18 Mar 2014 11:03:28 -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:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=R3coYDKGEbpzRpfO0jCc4xV8/71nVFchepc1A64Ivt4=; b=i0gK9HYxegpPBLvTC4Ftypt1kbcaQ3AQhgXJp9+UvIfb/QLM1wl5FoadhSw/UyfWVn 8gGd90/Qfmq1e6ZjP8QOUc+zk/lyIQ2S2iSaAP/l4es3m3gVoeZYIfKUul5Kr2GcgVfO g+IEsBtsQxnwKA6c3RMUKKa33FQTMyql8EXWL5+5REyw6/aumh7OR2iA5eff5dnqmTwv GZnftAPk4uKONMNODWIzWt8irtDDvqMjdTYDAK4KW39ZMYX371kcbmvIDg4SOx4+7sYM OR3ZzSHkGQCIQQHgpeuF6gq7phHicDatol/7csZifymseecd/sZT4kUycjRvUwt3V+CL 2HNQ== X-Gm-Message-State: ALoCoQnxpYFGjMykwQVaNGpEz6Xmw95GTFfMhDexwa8iEOzafNSUSRZo2BibMX/3f6vyFMH23Ga+ X-Received: by 10.182.250.200 with SMTP id ze8mr1292313obc.72.1395165808399; Tue, 18 Mar 2014 11:03:28 -0700 (PDT) Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by mx.google.com with ESMTPSA id c9sm25359660obq.20.2014.03.18.11.03.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Mar 2014 11:03:27 -0700 (PDT) Received: by mail-ob0-f171.google.com with SMTP id wn1so7264802obc.2 for ; Tue, 18 Mar 2014 11:03:27 -0700 (PDT) X-Received: by 10.60.60.33 with SMTP id e1mr27997955oer.36.1395165807770; Tue, 18 Mar 2014 11:03:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.74.9 with HTTP; Tue, 18 Mar 2014 11:02:47 -0700 (PDT) In-Reply-To: References: From: Ryan Mohr Date: Tue, 18 Mar 2014 08:02:47 -1000 Message-ID: Subject: Re: Faster one-time replication doing file-system copy? To: user Content-Type: multipart/alternative; boundary=089e013c5d2e6002df04f4e55a4e X-Virus-Checked: Checked by ClamAV on apache.org --089e013c5d2e6002df04f4e55a4e Content-Type: text/plain; charset=ISO-8859-1 For a while now I've wished couchdb had a fork feature to speed up initial replication times like this. curl -X POST -d '{"source":"db1","target":"db2"}' http://localhost:5984/_fork Basic process would be something like: 1. Do a simple file system copy to create the new db 2. Set the replication checkpoint on the source db 3. [Optional] Trigger a replication to carry over any doc updates that occurred during the process I imagine this would be easy to add same host, same couchdb instance... probably even same host, different instances. Gets a lot trickier when you need to copy across hosts though. --089e013c5d2e6002df04f4e55a4e--