nickva commented on issue #4035: URL: https://github.com/apache/couchdb/issues/4035#issuecomment-1136478622
@jeydude makes sense. When you switched from snappy to `none`, that was the same database? In other words, snappy was used, db was filled with data, then compression was switched to none? Or, did you create a new database, after switching compression to none, and then filled it with all the data? The issue could still be with the snappy compression as switching compression doesn't re-compress the data already written to disk. Perhaps somehow your view files got corrupt, if you have ability you can try to reset your view and let it rebuild. Try using `deflate_6` compression (that's what we use at Cloudant by default). A more drastic fix could be to switch to `deflate_6`, re-create the db using a larger sharding factor, say Q=16 if your database is that large, and replicate your data into that database. That way your view files would be smaller and may be build faster. -- 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: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
