nickva commented on issue #4994: URL: https://github.com/apache/couchdb/issues/4994#issuecomment-1965492535
That happens when a view shard is opened but has a view signature that's not current. It comes from https://github.com/apache/couchdb/blob/29db2df901207d67e1975ca11a091bcb7f46abcc/src/couch_mrview/src/couch_mrview_index.erl#L141 The expected signature matches file path: ``` binary:encode_hex(<<250,122,26,158,93,183,246,135,53,41,41,158,169,41,218,173>>). <<"FA7A1A9E5DB7F6873529299EA929DAAD">> ``` The other one is: ``` binary:encode_hex(<<87,225,55,84,101,143,50,221,45,61,42,165,141,102,202,177>>). <<"57E13754658F32DD2D3D2AA58D66CAB1">> ``` I don't recall seeing this error too often. Is there any chance your view shard files were moved, copied, restored from backup from an much older couch instance, or mounted on a volume shared across multiple nodes? Is it easy to reproduce? Just happened once or it's a regular occurrence? > Then it triggers CPU usage and is not responsible CouchDB 3 nodes cluster. That's expected as the next action after the log is to reset the view shard and rebuild. So in other words, after the view rebuilds, it should be back to normal. -- 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]
