[
https://issues.apache.org/jira/browse/COUCHDB-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski reassigned COUCHDB-863:
--------------------------------------
Assignee: Filipe Manana
Yeah, that's where I was headed. Filipe, does it make sense to you?
> error log noise when a DELETE kills a replication
> -------------------------------------------------
>
> Key: COUCHDB-863
> URL: https://issues.apache.org/jira/browse/COUCHDB-863
> Project: CouchDB
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 1.0.1
> Reporter: Randall Leeds
> Assignee: Filipe Manana
> Priority: Trivial
> Attachments: 0001-couch_rep-termination-cleanup.patch,
> 0001-die-cleanly-when-local-replication-db-goes-away.patch,
> 0001-refactor-replication-shutdown.patch
>
>
> couch_ref_counter:drop will complain, dying with noproc, if the reference
> counter does not exist.
> couch_rep listens for the 'DOWN' message but then tries to terminate, closing
> both source and target dbs. If either one was the source of the 'DOWN'
> message because it was deleted, this causes loud complaints in the log and
> gen_server exits. We can do this more cleanly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
