[
https://issues.apache.org/jira/browse/COUCHDB-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757919#action_12757919
]
Adam Kocoloski commented on COUCHDB-506:
----------------------------------------
The second case looks like a bug in _changes ... if a DB is deleted in the
middle of a continuous _changes feed we get an extra set of headers in the
response:
GET
/test_suite_db_b/_changes?style=all_docs&heartbeat=true&since=0&feed=continuous
HTTP/1.1
Accept: application/json
User-Agent: CouchDB/0.11.0a817251
Host: 127.0.0.1:5984
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Server: CouchDB/0.11.0a817251 (Erlang OTP/R13B)
Date: Mon, 21 Sep 2009 15:12:59 GMT
Content-Type: application/json
Cache-Control: must-revalidate
HTTP/1.1 500 Internal Server Error
Server: CouchDB/0.11.0a817251 (Erlang OTP/R13B)
Date: Mon, 21 Sep 2009 15:13:10 GMT
Content-Type: application/json
Content-Length: 55
Cache-Control: must-revalidate
{"error":"badmatch","reason":"{not_found,no_db_file}"}
> 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
>
> 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.
