From user-return-13561-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Mon Nov 08 12:46:23 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 79566 invoked from network); 8 Nov 2010 12:46:23 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Nov 2010 12:46:23 -0000 Received: (qmail 95427 invoked by uid 500); 8 Nov 2010 12:46:53 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 95200 invoked by uid 500); 8 Nov 2010 12:46:49 -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 95187 invoked by uid 99); 8 Nov 2010 12:46:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 12:46:48 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 12:46:40 +0000 Received: by fxm12 with SMTP id 12so3835535fxm.11 for ; Mon, 08 Nov 2010 04:46:18 -0800 (PST) Received: by 10.223.110.148 with SMTP id n20mr3683871fap.48.1289220378259; Mon, 08 Nov 2010 04:46:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.74.132 with HTTP; Mon, 8 Nov 2010 04:45:57 -0800 (PST) X-Originating-IP: [188.80.235.111] From: Marco Monteiro Date: Mon, 8 Nov 2010 12:45:57 +0000 Message-ID: Subject: seplication timeout problem To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=001636c5a28caef2e404948a02a2 --001636c5a28caef2e404948a02a2 Content-Type: text/plain; charset=ISO-8859-1 I'm trying to use CouchDB with Amazon's EC2 micro instances. These are very slow. There are no official numbers, but I think they are more or less equivalent to Pentium 2 at 200 MHz. I have 100 databases. There are 10 "master" databases and each has 10 "slave" databases. Each of the 10 master databases has many documents (around 50,000); the slaves start with no documents. I want to have continuous filtered seplication between each master and its slaves. When I start the continuous seplications, I get lots of timeouts in the seplication processes. I think that part of the problem is the communication with the JavaScript process for running the filters. These would go away if I implemented the filters in Erlang, right? Anyway, I'm trying to tweak the configuration to prevent the timeouts. I'm specifically playing with os_process_timeout, which I understand, and with max_http_sessions, max_http_pipeline_size, which I don't understand. What do these do? Anybody has any advice for me to get rid of the timeouts? Any other option in the configuration option that I can use? Thanks, Marco --001636c5a28caef2e404948a02a2--