[
https://issues.apache.org/jira/browse/COUCHDB-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500801#comment-14500801
]
Russell Branca commented on COUCHDB-2657:
-----------------------------------------
Thanks for the report [~robertkowalski]. I ported the test script to Python [1]
and I'm able to reproduce these issues. Deleting the _metadata db and rerunning
the test works, but I haven't been able to test a fresh start of the dev
cluster without the _metadata db as it keeps getting recreated.
[~ilyak] where are you observing those failures? Is that during the first run
of setup? I'm not seeing those.
[1] https://gist.github.com/chewbranca/44e266140cbb74db9c47
> if _metadata is there, creating a db does not work
> --------------------------------------------------
>
> Key: COUCHDB-2657
> URL: https://issues.apache.org/jira/browse/COUCHDB-2657
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: BigCouch, Database Core
> Reporter: Robert Kowalski
> Priority: Blocker
>
> with the new _setup_cluster endpoint a _metadata db is created.
> when it exists, and we create a db, read it _all_doc immediatly [1] (Fauxton
> does that) we get:
> `document update conflict`
> [1]
> http://localhost:8000/sdfsdtest/_all_docs?startkey=%22_design%2F%22&endkey=%22_design0%22&include_docs=true&limit=501
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
