Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/102#issuecomment-142240332
There is a problem with shards:
```
$ http put
http://localhost:15984/ebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617ad
HTTP/1.1 201 Created
Cache-Control: must-revalidate
Content-Length: 12
Content-Type: text/plain; charset=utf-8
Date: Tue, 22 Sep 2015 10:14:44 GMT
Location:
http://localhost:15984/ebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617ad
Server: CouchDB/cb58087 (Erlang OTP/18)
X-Couch-Request-ID: 6f65159f96
X-CouchDB-Body-Time: 0
{"ok":true}
$ http get
http://localhost:15984/ebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617ad
HTTP/1.1 500 Internal Server Error
Cache-Control: must-revalidate
Content-Length: 91
Content-Type: text/plain; charset=utf-8
Date: Tue, 22 Sep 2015 10:16:16 GMT
Server: CouchDB/cb58087 (Erlang OTP/18)
X-Couch-Request-ID: 757fde0712
X-Couch-Stack-Hash: 931695309
X-CouchDB-Body-Time: 0
{"error":"internal_server_error","reason":"No DB shards could be
opened.","ref":931695309}
```
Obliviously, there are no shards, because:
```
mem3_shards tried to create
shards/e0000000-ffffffff/ebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617ad.1442916620,
got
{error,{database_name_too_long,<<"shards/e0000000-ffffffff/ebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617bbebd6af834f824cff9f8b4ed4bb6617ad.1442916620">>}}
```
So technically PR is correct, but not for shards. Revoking my +1. Sorry for
missing that case.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
