[
https://issues.apache.org/jira/browse/COUCHDB-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089982#comment-16089982
]
ASF subversion and git services commented on COUCHDB-3423:
----------------------------------------------------------
Commit 38cc13957debe6f34b328b9a3f0cb86a7eff0dfb in couchdb's branch
refs/heads/master from [~tonysun83]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=38cc139 ]
catch database not exist error
If dbs do not exist, we catch the error for mem3_sync_security
so that it can continue for databases that do exist.
https://github.com/apache/couchdb/pull/538
COUCHDB-3423
> fix sync security when db count is large
> ----------------------------------------
>
> Key: COUCHDB-3423
> URL: https://issues.apache.org/jira/browse/COUCHDB-3423
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Tony Sun
>
> When we execute mem3:sync_security/0, we all fabric:all_dbs/0. This call can
> take a long time if the number of dbs is large. During this time, users can
> delete dbs and when this occurs will cause an database_does_not_exist EXIT.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
