New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replication suspended #1155
Comments
Resetting or switching to a new database locally solves it but if a client has unsynced changes they obviously get lost. :/ |
Hey @andrezimpel . Which versions of the client and the server are you using? Could you enable debug logging on the client and share the log output from the browser console leading up to the moment when replication gets suspended? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my server logs I can the message "Outgoing replication to the client is suspended because there are 30 unacked transactions" constantly. Also changes stoped syncing across clients. I don't really know how to track the issue down or to give more context right now. Help is appreciated a lot!
The text was updated successfully, but these errors were encountered: