[bisq-network/bisq] Unsynced DAO state forcing to restart Bisq in order to fix sync (Issue #6073)

[chimp1984]

Agree with @jmacxx 
The data limitation issues should be fixed by now. In the logs it can be seen if that is an issue, but I highly doubt.
I think there is a bug in the snapshot handling and/or peristence for DAO data. With separating DAO blocks and DaoState we introduced more risk that DAO data gets out of sync (before it was all in the DaoState, thus lower risk but it became a scalability problem).

The bug is not trivial to find. I would suggest to add lot of logs into that code area and hopefully it will help to reveal where the issue gets caused. A very critical code review about all that code paths might help as well.
I am offline the next days....

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/6073#issuecomment-1049251651
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/issues/6073/1049251651 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220223/f9d324b7/attachment.htm>