couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kowalski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2657) if _metadata is there, creating a db does not work
Date Fri, 10 Apr 2015 00:45:12 GMT

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

Robert Kowalski commented on COUCHDB-2657:
------------------------------------------

it looks like a race condition, i can reproduce it with this script that i run multiple times
(sometimes the bug appears, sometimes not): https://gist.github.com/robertkowalski/ad59db3085e76ff27452

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

Mime
View raw message