-
Notifications
You must be signed in to change notification settings - Fork 456
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
Handling server restart gracefully #358
Comments
Have you tried with the latest version from github? There were some changes in the code that made a lot of these notifications more resilient if I remember correctly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey ShareJS team,
I'm using the inmemory livedb. When my server restarts, the documents are destroyed, which is fine. The problem is that there seems to be no way to notify clients that their document is destroyed. As a client, this is what the log shows:
Then when the server recovers:
The client stays in this state until the client tries to make a change, upon which the server crashes with "document not found" and the client gets this:
I would like to change this behavior so that, when the client reconnects to the server, it detects that the server has restarted. I can then handle the document being destroyed correctly on the client side. Can I catch that "Ignoring attempt to ingest..." warning? How do I handle this case?
Thanks!
Jason G, sole developer of Tidalwave: https://github.com/MisterTea/TidalWave
The text was updated successfully, but these errors were encountered: