We are using Cosmos with MongoDB API ver 4.0 with change streams
From the Microsoft Documentation we understood that Default MAX Cosmos Connection Pool Size =100
If we open 'n' change stream to WATCH on any collection , Will CosmosDB consider creating 'n' connections ?
ie.. will each WATCH operation on Cosmos consumes one dedicated connection from the Connection Pool?
We set the Max Connection Pool Size as '2' & tried creating more than 2 Change Streams. We observed that the call is never returned , For the 3rd change stream .
Is this expected result?
If we open more than 100 change streams (Considering the Pool Size as 100) Assuming that all WATCH processes are running indefinitely without
releasing the connection back to the POOL , Will this affects the Performance ?
Kindly confirm ,
Will more number of change streams required larger pool size to be set on CosmosDB ?
Similar to mongodb -https://jira.mongodb.org/browse/DOCS-11270
Whether opening multiple Change streams will affect performance ?
Similar to mongodb https://jira.mongodb.org/browse/SERVER-32946
Awaiting for your suggestion/Feedback
Thanks & Regards