> On 09 Mar 2015, at 23:18, Tito Ciuro <[email protected]> wrote: > > Hello, > > I have a CouchDB with millions of docs. One of the views has exactly one > document to store acls (doc_type == 'acl'). The design doc hasn't changed in > a long time. Today, I upgraded the server (same CouchDB version, same DB) and > quickly realized that CouchDB was reindexing the acl view. > > It's crazy because we didn't changed anything and it's affecting server > performance. The question is, why would this happen? Could it be that the acl > b-tree got corrupted and needed a reindexation? If our users see that, it > would give them a bad impression, which worries me.
Did you change anything other view in the same design doc? How did you upgrade the system? What happened to running processes? When upgrading the server, did you migrate the data? Did you include the database_dir/.dbname-design directory/ies? It is unlikely that CouchDB corrupted the view index on its own, but some upgrade procedure might have caused an issue. If you only have a single doc for ACLs, I’d recommend using a doc id with a well-known name, like `acl` instead of a view to find it. Best Jan --
signature.asc
Description: Message signed with OpenPGP using GPGMail
