[
https://issues.apache.org/jira/browse/COUCHDB-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski closed COUCHDB-506.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.10
The broken _changes feed when a DB was deleted mid-response was fixed in
r817398. The replicator will quietly start a new connection if the changes
feed goes down as of r817400. I also tried to put in some code to slim down
the error messages when one of the DBs in a replica pair is deleted, but it
could still use some more work.
All of this has been merged to the 0.10 release branch.
> error when source is down with continuous replication
> -----------------------------------------------------
>
> Key: COUCHDB-506
> URL: https://issues.apache.org/jira/browse/COUCHDB-506
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 0.10
> Reporter: Benoit Chesneau
> Assignee: Adam Kocoloski
> Fix For: 0.10
>
>
> When source of continuous replication hangs or is down I get this error in
> lofs :
> [error] [<0.46.0>] {error_report,<0.21.0>,
> {<0.46.0>,supervisor_report,
> [{supervisor,{local,couch_rep_sup}},
> {errorContext,shutdown_error},
> {reason,{error,connection_closed}},
> {offender,
> [{pid,<0.100.0>},
> {name,"1b64e359f0f62e0921c6569e13907689+continuous"},
> {mfa,
> {gen_server,start_link,
> [couch_rep,
> ["1b64e359f0f62e0921c6569e13907689",
> {[{<<"source">>,<<"http://192.168.1.3:5984/db0";>>},
> {<<"continuous">>,true},
> {<<"target">>,<<"db0">>}]},
> {user_ctx,null,[<<"_admin">>]}],
> []]}},
> {restart_type,transient},
> {shutdown,1},
> {child_type,worker}]}]}}
> Seem like couchdb continue to work but imo this should be an expected error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
