[
https://issues.apache.org/jira/browse/COUCHDB-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852510#action_12852510
]
Randall Leeds commented on COUCHDB-722:
---------------------------------------
I'm rather confused.
The compaction seems to be on the service-metrics database, but the replication
is between databases named node-metrics.
However, there's a POST to /service-metrics/_missing_revs on the target
database right around the time compaction completes. Replication performs this
operation. Are you using vhosts or some kind of proxy layer that's rewriting
any of your requests? Could you include a little bit more context at the end
where you put the ...? In particular I want to know if the replication was
using the service-metrics database at all.
> Continuous replication tasks fail
> ---------------------------------
>
> Key: COUCHDB-722
> URL: https://issues.apache.org/jira/browse/COUCHDB-722
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 0.11
> Environment: Arch Linux, CouchDB 0.11
> Reporter: Fredrik Widlund
>
> Couchdb 0.11.0 replication tasks fails with the below after working for
> everything from a few minutes to an hour. The below replication is of the
> type {"source":"http://127.0.0.1:5984/node-metrics";,
> "target":"http://1.2.3.4:5984/node-metrics";, "continuous":true} and the
> node-metrics database exist on both machines.
> The database is periodically compacted which, and I'm speculating here, could
> be a contributing factor to the crash.
> Kind regards,
> Fredrik Widlund
> =CRASH REPORT==== 1-Apr-2010::14:25:26 ===
> crasher:
> initial call: couch_rep:init/1
> pid: <0.274.0>
> registered_name: []
> exception exit: {{badmatch,
> {stop,
> {db_not_found,
> <<"http://127.0.0.1:5984/node-metrics/";>>}}},
> [{couch_rep,do_checkpoint,1},
> {couch_rep,handle_cast,2},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]}
> in function gen_server:terminate/6
> ancestors: [couch_rep_sup,couch_primary_services,couch_server_sup,
> <0.32.0>]
> messages: [{'EXIT',<0.21084.1>,normal}]
> links: [<0.81.0>]
> dictionary: [{task_status_update,{{1270,124726,124009},0}}]
> trap_exit: true
> status: running
> heap_size: 10946
> stack_size: 24
> reductions: 29173458
> neighbours:
> [error] [<0.81.0>] {error_report,<0.31.0>,
> {<0.81.0>,supervisor_report,
> [{supervisor,{local,couch_rep_sup}},
> {errorContext,child_terminated},
> {reason,
> {{badmatch,
> {stop,
> {db_not_found,<<"http://127.0.0.1:5984/node-metrics/";>>}}},
> [{couch_rep,do_checkpoint,1},
> {couch_rep,handle_cast,2},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]}},
> {offender,
> [{pid,<0.274.0>},
> {name,"f3e3081db5a215dbaf9b2984f0552090+continuous"},
> {mfa,
> {gen_server,start_link,
> [couch_rep,
> ["f3e3081db5a215dbaf9b2984f0552090",
> {[{<<"target">>,
> <<"http://1.2.3.4:5984/node-metrics";>>},
>
> {<<"source">>,<<"http://127.0.0.1:5984/node-metrics";>>},
> {<<"continuous">>,true}]},
> {user_ctx,null,
> [<<"_admin">>],
> <<"{couch_httpd_auth,
> default_authentication_handler}">>}],
> []]}},
> {restart_type,temporary},
> {shutdown,1},
> {child_type,worker}]}]}}
> =SUPERVISOR REPORT==== 1-Apr-2010::14:25:26 ===
> Supervisor: {local,couch_rep_sup}
> Context: child_terminated
> Reason: {{badmatch,
> {stop,
> {db_not_found,
> <<"http://127.0.0.1:5984/node-metrics/";>>}}},
> [{couch_rep,do_checkpoint,1},
> {couch_rep,handle_cast,2},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]}
> Offender: [{pid,<0.274.0>},
> {name,"f3e3081db5a215dbaf9b2984f0552090+continuous"},
> {mfa,
> {gen_server,start_link,
> [couch_rep,
> ["f3e3081db5a215dbaf9b2984f0552090",
> {[{<<"target">>,
> <<"http://1.2.3.4:5984/node-metrics";>>},
> {<<"source">>,
> <<"http://127.0.0.1:5984/node-metrics";>>},
> {<<"continuous">>,true}]},
> {user_ctx,null,
> [<<"_admin">>],
> <<"{couch_httpd_auth,
> default_authentication_handler}">>}],
> []]}},
> {restart_type,temporary},
> {shutdown,1},
> {child_type,worker}]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
