Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <33368119.239111290452713508.JavaMail.jira@thor>
Date: Mon, 22 Nov 2010 14:05:13 -0500 (EST)
From: "Adam Kocoloski (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-962) Badarg error in HTTP request
In-Reply-To: <2377501.239021290452475491.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934560#action_12934560 ] 

Adam Kocoloski commented on COUCHDB-962:
----------------------------------------

I recommended that Bradley file this bug report after a bit of conversation on IRC.  It sounds like the document can usually be retrieved ok, but occasionally it hits this stacktrace instead.  A restart of CouchDB clears the issue.  I'm fairly stumped at the moment about what could cause this.


> Badarg error in HTTP request
> ----------------------------
>
>                 Key: COUCHDB-962
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-962
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: RHEL5, Erlang r12b-5
>            Reporter: Bradley Holt
>
> During an attempt to open a document, CouchDB tries to read a btree node from a given offset in the file, but that offset points to an actual document ID rather than a serialized btree node. You can see the relevant log entries here:
> https://gist.github.com/710375
> Note that this error always appears to happen with the same document. At last count, this document had 3,576 revisions (above the threshold where stemming kicks in).

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