rnewson commented on issue #5612: URL: https://github.com/apache/couchdb/issues/5612#issuecomment-3144697849
a rev of 53 implies this database has been created/recreated many times and I wonder if you now have a conflicted _dbs document that might explain these symptoms? I agree that mem3 should not be trying to sync a node it doesn't know about (indeed, it can't do so) and that you've done the typical steps to remove a node (removing it from the _nodes db and removing it from the shard maps of all databases). The "changelog" section is for information only, the code doesn't look at it for anything important. simply put, couchdb must see `couchdb@172.16.7.221` in something or it wouldn't attempt internal sync to it. I'd look at the _dbs docs with `?conflicts=true` and see if there are any. Beyond that, I think better to jump into the couchdb slack workspace and we can assist more easily than here. -- 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
