Firestore client stops functioning after 100 snapshot listeners are registered

[nikammerlaan]

I've run into an issue with my application where all requests (get/set/update/queries) and listeners stop functioning after the 100th one is added (the first 100 listeners still function, all ones added after just sit idle and never receive any events). If I had to guess what could be causing the issue, I'd guess that there is probably a saturated threadpool somewhere. I tried to look around in the source for that but I couldn't find what I was looking for.

Edit: After doing some more investigating, it seems that all requests (get, set, update, query, etc)block after that 100th listener is added.

[schmidt-sebastian]

@nikammerlaan Thanks for reporting this issue! This is actually a limitation of our network stack. By default, we only support 100 concurrent streams. If you are hitting this limit, you can change the number of connections in the pool. To change the setting you can do the following:

Builder options =  FirestoreOptions.newBuilder().build().toBuilder();
options.setChannelProvider(
   FirestoreOptions.getDefaultTransportChannelProviderBuilder().setPoolSize(2).build());
firestore = options.build().getService();

We allow 100 streams per entry in the pool, but you can adjust this setting as needed. Note that introduces some overhead, as each connection requires its own setup.

[appsgenie]

Does this mean 100 total snapshots across all clients for the entire database or 100 from one client (either a mobile device or with admin sdk)?

[lucazin]

I have this kind of problem @schmidt-sebastian

i have 7 listeners, but always disconnecting some listeners and stop registering information in database. Im using Java.

What i have to do..to stop this behavior..?? because its intermitent situation.

I have to move to realtime database? or have some config extra to fix that? Because when i restart the server the listener back again..