Gidsik commented on issue #5909: URL: https://github.com/apache/couchdb/issues/5909#issuecomment-4015121311
@rnewson Thank you for looking into this. I was able to reproduce the problem on another device, with the same Windows 11 + Docker Desktop on wsl2 setup. Also I asked a friend of mine to install wsl + docker desktop on his win10 machine and run commands to reproduce issue and it is indeed reproducible. I respect your experience and understand that you, as developers, have worked with various configurations and environments! But seems like this is real and reproducible issue with couchdb setup in **Docker Desktop** specifically (only wsl2 backend or hyper-v backend too???). I think regular unix docker works fine otherwise you would have known and fix this a long time ago. I understand that docker desktop is not a priority as it is not a common configuration and is not intended for production or large customers and enterprises, as most of them are using either unix systems and containers/clusters with k8s etc., or windows binaries with windows server. But I hope that couchdb team will consider to add some kind of fallback over this specific error so database wont became inaccessible or at least add some note about this issue in documentation and provide advice\configuration to avoid such error for users who wants to setup couchdb in docker desktop. I managed to mitigate the issue in my setup by setting `smoosh.db_channels = ratio_dbs` and `smoosh.ratio_dbs.min_priority = 5.0` with very thin `smoosh.overnight_channel` basically preventing compaction from triggering. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
