nickva opened a new issue, #5980: URL: https://github.com/apache/couchdb/issues/5980
### Version unknown ### Describe the problem you're encountering We have observed that when design docs are updated, and specifically deleted, index update processes are still left running on some of the nodes in the cluster This stems from the fact that ddoc_update events from couch_db_updater are sent to the local event handler and then handled locally on that node https://github.com/apache/couchdb/blob/f7cb246cd54c2518a40df00e74b85996664a0402/src/couch_index/src/couch_index_server.erl#L361-L368 Design documents in CouchDB do not live locally on every shard, instead they are each in their own set of shard copies based on the hash of the their Doc ID, just like every other regular document. That means that when a design document changes, only indexer processes running on the same node as the design doc shard will be shut down. The ones with shards on nodes where there are no design doc copies will be left running. ### Expected Behaviour When a design document changes we clean up all the stale index processes on all the nodes ### Steps to Reproduce _No response_ ### Your Environment _No response_ ### Additional Context _No response_ -- 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]
