couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] Commented: (COUCHDB-455) get_result,infinity error when replicating an empty database
Date Thu, 06 Aug 2009 16:12:14 GMT


Adam Kocoloski commented on COUCHDB-455:

Hi Enda, thanks for the report.  I have to admit I'm a bit stumped at first.  The error message
indicates that the replication gen_server had exited before the call to get_result.  Couch
0.9.0 and higher should protect against that.  Were there any other related error messages?

There is one scenario I can dream up.  Are you triggering that same replication multiple times
simultaneously?  That is

A POSTs to _replicate
B POSTs to _replicate with identical request body
A receives a response, replicator shuts down
B gets a noproc error

In this case we try to add B as a listener to the original replication, but it's technically
possible the replication could terminate in between when B gets the process id and when it
asks for the result.

> get_result,infinity error when replicating an empty database
> ------------------------------------------------------------
>                 Key: COUCHDB-455
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9
>            Reporter: Enda Farrell
> We have code that regularly calls for CouchDB nodes to replicate with pairs in our other
datacentre. It ocassionally has the follwing error:
> {code}
> INFO 371 - Bad replication: [
<- (ACE_METADATA_) {"source":"","target":"tvp_yahoowidgets"}]:
response:[HTTP/1.1 500 Internal Server Error - {"error":"noproc","reason":"{gen_server,call,[<0.17199.212>,get_result,infinity]}"}
> {code}
> The remote database "" is empty:
> {code}curl
> {"db_name":"tvp_yahoowidgets","doc_count":0,"doc_del_count":0,"update_seq":0,"purge_seq":0,"compact_running":false,"disk_size":5920,"instance_start_time":"1249559096646177"}
> {code}
> This same "get_result,infinity", is seen on another empty database:
> {code}
> curl
> {"db_name":"avalanche150k","doc_count":0,"doc_del_count":0,"update_seq":0,"purge_seq":0,"compact_running":false,"disk_size":250480,"instance_start_time":"1249559230162131"}
> {code}

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

View raw message