You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/07/27 15:22:56 UTC

[GitHub] browndav commented on issue #1119: Could not open shard

browndav commented on issue #1119: Could not open shard
URL: https://github.com/apache/couchdb/issues/1119#issuecomment-408452048
 
 
   Is the working theory still that this is Docker-related? I'm unaware of any virtualization going on with Docker on Linux (it's kernel namespacing, and we've verified by hand in C that normal file operations such as `open(2)`, `write(2)`, `read(2)`, and `fsync(2)` work as expected in-container and perform at native speeds).
   
   We're experiencing this issue and cannot come up with a theory as to why a database-level RPC failure would be related to Docker's namespacing/isolation.
   
   Is there any more information available here, or could you perhaps share any working theories on what specifically might be causing this and what subsystem(s) (e.g. at the CouchDB level, at the Erlang level, at the system level) you currently suspect?
   
   Thanks in advance.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services