Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <858229.56131286653484061.JavaMail.jira@thor>
Date: Sat, 9 Oct 2010 15:44:44 -0400 (EDT)
From: "Paul Joseph Davis (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-644) Replicator creates URLs which are too
 long for the source node
In-Reply-To: <662833154.152041265731047958.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis updated COUCHDB-644:
--------------------------------------

    Skill Level: Regular Contributors Level (Easy to Medium)

> Replicator creates URLs which are too long for the source node
> --------------------------------------------------------------
>
>                 Key: COUCHDB-644
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-644
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 0.9
>         Environment: couchdb 0.9.0.r766883 CentOS x86_64 
>            Reporter: Enda Farrell
>            Priority: Critical
>         Attachments: urls.too.long.100
>
>
> We have an environment which can on ocassion create many open revs of a doc. The URLs that the replicator creates are longer than the http://issues.apache.org/jira/browse/COUCHDB-243 "mochiweb has an 8k limit", resulting in a general server crash. 
> To date the only work-around identified is to "export" the latest revisions of all docs in the database, destroy the database, re-create the database and reload the exported documents.
> On one of our environments we have:
> These docs have the trouble:
>     * http://db015.back.test.cwwtf.local:5984/labuk_braintestbritain/training_sessions_2255838
>     * http://db015.back.test.cwwtf.local:5984/madcache8888/b0019gpg
>     * http://db015.back.test.cwwtf.local:5984/madcache/bbc_one_scotland
>     * http://db015.back.test.cwwtf.local:5985/labuk_braintestbritain/training_sessions_1910457
>     * http://db015.back.test.cwwtf.local:5985/madcache8888/p0031rr3
>     * http://db015.back.test.cwwtf.local:5985/madcache/MAD_last_update
> Their requests length - path + params (ie no host:port) are shown here (the key) with the number of times that that length was seen in our log files (the count):
> key => count
> 8544 => 24
> 8557 => 11
> 8568 => 2392
> 8572 => 55
> 8591 => 893
> 8594 => 45
> 8636 => 27
> Attached is a file with a sample of these too-long URLs. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.