jvegaseg opened a new issue #1460: Replaced broken node has more data space than expected URL: https://github.com/apache/couchdb/issues/1460 <!--- Provide a general summary of the issue in the Title above --> We have a 6-node cluster configured with q=16. We are using version 2.1.1 We lost one of the nodes and we replace it with a new one. Before being replaced, the directory /opt/couchd/data had a disk space size of 3,3Tb. After the replacement, same directory has a disk space size of 5,6 Tb. Why this extra disk space? ## Expected Behavior Node replaced should have similar data space than previous one. ## Current Behavior There are more disk space for data than expected. ## Possible Solution No idea. ## Steps to Reproduce (for bugs) Replacing a broken node. ## Context <!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world --> ## Your Environment Software is running on virtualized Centos 7 using OpenVZ 7. Each node has same configuration. Each node has 16 cores and 10 Tb of disk space.
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
