-
Notifications
You must be signed in to change notification settings - Fork 373
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
Firestore Realtime listener drops a connection and does not reconnect #119
Comments
Hey there! I couldn't figure out what this issue is about, so I've labeled it for a human to triage. Hang tight. |
Hmmm this issue does not seem to follow the issue template. Make sure you provide all the required information. |
This should probably be reported at https://github.com/googleapis/nodejs-firestore @schmidt-sebastian can you take a look? |
@saminiemi We have retry logic in place to handle this specific situation. If you can reproduce this failure regularly, do you mind turning on debug logging and sending us the logs from just before this occurred? You can do this as follows:
|
Thanks @schmidt-sebastian . We did like suggested and here is the result:
Seems to be something to do with authentication. Hope this helps and if there is any information you would like me to provide, please let me know. |
I can also confirm that most of the time listener survived just fine:
|
We also have caught following error:
And this. We have paid plan, so I wonder which quota this might be.
|
Hi, is there an update on this issue? Was the solution found? |
Hello! @schmidt-sebastian any update on this one? We are still getting this regularly, at least once in a day. Tried it also on Debian-based docker container, with same result. Most of the time error log looks like this:
|
These log statements are very helpful. Our retry logic considers these streams as healthy once it is able to send out a network package ("Marking stream as healthy"). Unfortunately, just because the TCP layer accepts our packages, doesn't necessarily indicate that the outbound network link is active. We may have to retry more aggressively. I will kick off an internal discussion. |
Hi. I have the same problem. With onSnapshot method.
Firebase console:
And earlier today:
Please solve this issue. I making app which I have to give to the client next week ! All last days I spent over looking for bugs in my application but nothing found. |
We are aiming to push a release that addresses these network issues within the next two weeks. |
Thanks @schmidt-sebastian . That is great news! Hopefully this new version of googleapis/nodejs-firestore is included to firebase-admin-node soon 👍 |
We are targeting a release next week. |
Are you sure it solved that bug? Cuz I'm still having it |
I just relaxed our retry condition even further. If you have a chance, do you mind patching in googleapis/nodejs-firestore#82 ? Thanks. |
i have this same problem with java service, snapshot stop until restart server. |
We have a simple Firestore Realtime listener running on Docker container at Google Container Engine. Few times, listener for some reason have lost a connection and does not reconnect. Updates (sets, updates and deletes) does work but we don't get notifications of updates, until we restart a container.
Error message we have got couple of times during last week:
Once (first time) we have got this:
Our code is basically like this:
Is listener planned to survive on these situations, or should be build some kind retry system by ourselves?
Thanks!
The text was updated successfully, but these errors were encountered: