nickva commented on issue #5130:
URL: https://github.com/apache/couchdb/issues/5130#issuecomment-2237029781
We were able to model the `nonode@nohost` result from `nodes()` state by
noticing that it happen when the `net_kernel` dist controller process is
killed. The VM will exit, but in the process of shutting down for a period of
time `node()` returns `nonode@nohost`. The sequence rewind still remains a
mystery, though.
So far we've put in couple of fixes related to this:
* https://github.com/apache/couchdb/pull/5132 introduces a permanent node
name that saves the initial `node()` in a persistent term and does value
validations right after in `config`, then asserts during epoch updates that the
sequence rewinds.
* https://github.com/apache/couchdb/pull/5138 uses the persistent node
name in a few more cases when there is a likelihood of the `nonode@nohost`
affecting persistent data (checkpoints, shard maps, logs)
Closing the issue for now. We'll monitor to see if we notice any assertion
triggers on sequence rewinds and re-open it then to continue working on it.
--
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
