[ 
https://issues.apache.org/jira/browse/COUCHDB-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143742#comment-14143742
 ] 

Robert Newson commented on COUCHDB-2334:
----------------------------------------

I think we should address the initial cluster startup story directly. I'd be 
quite happy to see a requirement to create the metadata db before the clustered 
interface becomes usable. That is, all operations simply fail until the cluster 
is configured properly, and we don't need to log it.

At the risk of opening a giant can of worms, I don't think "cassim" is 
immediately obvious to people that this is a special database that replaces the 
_security objects. While we were free, at Cloudant, to choose cute names, I 
think CouchDB ought to be a bit more obvious (if boring) in its component 
names. I suggest _meta for the database name, at least (since we do plan to 
store more than _security documents) but it's just one suggestion. I don't 
think we *need* to rename the cassim application unless someone feels strongly 
about that (I think we can pitch the "open sesame" / security thing just fine).

Anyway, the central idea here is to define a pre-production state for the 
cluster, where the administrator has to complete some steps before it will 
work. This could be a simple endpoint that the administrator uses to say that, 
yes, actually the 'nodes' db is now fully populated. When that happens, we can 
create all three dbs, _users, _replicator, _meta (or whatever it's called).


> Metadata db "cassim" does not exist
> -----------------------------------
>
>                 Key: COUCHDB-2334
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2334
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: BigCouch
>            Reporter: Alexander Shorin
>
> And so happens every 5 minutes:
> {code}
> 2014-09-20 04:00:06.786 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:05:06.788 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:10:06.790 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:15:06.792 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:20:06.794 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:25:06.796 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:30:06.798 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:35:06.800 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:40:06.802 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:45:06.804 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:50:06.806 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 04:55:06.808 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 05:00:06.810 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 05:05:06.812 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> 2014-09-20 05:10:06.814 [error] [email protected] <0.341.0> Metadata db 
> "cassim" does not exist
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to