Open boweiliu opened 1 year ago
A workaround that works for me is https://github.com/firebase/firebase-tools/pull/5655 -- simply adding a timeout to the work queue workers seems to resolve the stalling, at the cost of some jobs which never get fired.
I'm also attaching the firestore emulator jar which appears to be the source of this stacktrace
OK nvm it's over the github comment upload limit, but it's cloud-firestore-emulator-v1.16.1.jar
Hi boweiliu,
Based on this line it seems related to RTDB? Do you have a repro case we can take a look at?
12:07:45.409 [TriggersWorkerPool-3-1] ERROR com.firebase.server.client.GCFEmulatorPublisher - rtdb failed to publish trigger to functions emulator with exception
com.firebase.server.client.ChannelClosedException$: The underlying socket was closed and released from the connection pool
I agree, it seems to be related to either RTDB or to pubsub, unfortunately I don't have a minimal test case right now.
Hey @boweiliu. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Can you share any debugging tools for sniffing the requests sent by the firebase emulator to the rtdb ? We're triggering them from the functions part of the firebase emulator which makes it quite difficult to nail down the minimal crash case.
[REQUIRED] Environment info
firebase-tools: 11.25.2
Platform: OSX
[REQUIRED] Test case
Crash/stalling behavior appears to happen more often when a number of concurrent requests are made from functions emulator to the firestore emulator.
[REQUIRED] Steps to reproduce
[REQUIRED] Expected behavior
Functions emulator workers should catch emulator-internal errors and trigger userspace functions reliably
[REQUIRED] Actual behavior