[
https://issues.apache.org/jira/browse/COUCHDB-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds updated COUCHDB-863:
----------------------------------
Attachment: 0001-refactor-replication-shutdown.patch
Here's another loose patch I think we should wrap up and close.
I just made replication shut down a little more clear but reducing code
duplication and moving some calls around. It also fixes the log noise. Info
level log messages will occur if a local db shuts down during replication but
there won't be any nasty backtraces about closing a db that's not open.
> 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
> Priority: Trivial
> Attachments:
> 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.
