sergey-safarov commented on issue #1119: Could not open shard
URL: https://github.com/apache/couchdb/issues/1119#issuecomment-362465655
 
 
   Joan (@wohali) on provided link is not used volumes and used disk image via 
loopback + docker filesystem overlay. You example is not applicable to this 
ticket.
   
   On my host is installed Fedora 27 operation system.
   For Fedora is 
[recommended](https://docs.docker.com/storage/storagedriver/select-storage-driver/)
   
   > |Linux distribution |Recommended storage drivers                           
                                |
   > 
|-------------------|--------------------------------------------------------------------------------------|
   > |Docker CE on Fedora|devicemapper, overlay2 (Fedora 26 or later, 
experimental), overlay (experimental), vfs|
   > 
   >When possible, overlay2 is the recommended storage driver. When installing 
Docker for the first time, overlay2 is used by default.
   
   But i use `volume` as permanent store for couchdb data and according this 
[page](https://docs.docker.com/storage/storagedriver/#data-volumes-and-the-storage-driver)
  is not mater what is used storage driver
   
   > A data volume is a directory or file in the Docker host?s filesystem that 
is mounted directly into a container. Data volumes are not controlled by the 
storage driver. Reads and writes to data volumes bypass the storage driver and 
operate at native host speeds.
   
   I have googled about slow disk operation inside docker container. I find 
only related to docker for MacOS (not linux).
   
   Also i have made test inside docker container
   ```
   [root@node0 ~]# docker run --rm -it -v test:/home fedora:27 /bin/sh
   sh-4.4# date; dd if=/dev/zero of=/home/test.img bs=1G count=10; date
   Fri Feb  2 02:19:51 UTC 2018
   10+0 records in
   10+0 records out
   10737418240 bytes (11 GB, 10 GiB) copied, 5.12558 s, 2.1 GB/s
   Fri Feb  2 02:19:56 UTC 2018
   sh-4.4# 
   ```
   Results is same to test on host operation system.
   
   
   

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to