couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-863) error log noise when a DELETE kills a replication
Date Wed, 20 Oct 2010 20:06:38 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Randall Leeds updated COUCHDB-863:
----------------------------------

    Attachment: 0001-couch_rep-termination-cleanup.patch

Hey, Adam. Thanks for catching the checkpoint issue and thanks for the review.
After thinking about what you said, there really isn't any reason to explicitly close the
dbs, delete the ets table, or even cancel the timer (double check me on the timer?).

So, here we go. 2 insertions. 20 deletions. Feels good, doesn't it ;).

> 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-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.


Mime
View raw message