nickva commented on issue #5612: URL: https://github.com/apache/couchdb/issues/5612#issuecomment-3145674785
@andres-mariano try https://couchdb.apache.org for a slack link, that used to work without needing an `apache@` email... Thanks for trying giving the `conflicts=true&include_docs=true` a try. It doesn't seem like there are any conflicts then. It does seem more and more like it's an issue with a job that's being retried indefinitely toward a non-existent node. If so, the issue would happen here: https://github.com/apache/couchdb/blob/d9a6ac5f470c424ee7ff35958bb0043386a72dc0/src/mem3/src/mem3_sync.erl#L160-L170 And it would manifest as a race-condition. If the node is removed while the job was running or was sleeping before a retry it seems it could end up in such a loop (attempt, crash, log warning, retry, attempt, crash, ...) To confirm if this is the case, if you restart your node this warning should stop. -- 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]
