Comment 2 for bug 1786258

Default pool limit, is in the gopkg.in/mgo.v2 code base is 4096 per
controller. You can set a value in agent.conf:
if limitStr := agentConfig.Value("MONGO_SOCKET_POOL_LIMIT"); limitStr != ""
{

Likely it will cause queries to just fail. w/ 3 HA controllers, max cons
would be 3*4096=12,288 connections. So you aren't currently hitting that.

On Mon, Aug 13, 2018 at 8:46 AM, John Meinel <email address hidden> wrote:

> We do pool connections. If the pool is in active use, we allow it to grow.
> Likely lots of agents were doing concurrent activity and we don't put hard
> caps on the pool.
>
> Likely we *should* be putting a cap on the pool, though it means we'll
> also have to handle when a thread is unable to make their request because
> they can't get a slot in the pool.
>
> It may just be a limiter/timeout sort of system (wait up to 50ms for a
> free slot to be available before creating a new connection).
>
>
> On Fri, Aug 10, 2018 at 3:17 AM, Tim Penhey <email address hidden>
> wrote:
>
>> ** Tags added: mongodb scalability
>>
>> ** Changed in: juju
>> Status: New => Triaged
>>
>> ** Changed in: juju
>> Importance: Undecided => Medium
>>
>> --
>> You received this bug notification because you are subscribed to juju.
>> Matching subscriptions: juju bugs
>> https://bugs.launchpad.net/bugs/1786258
>>
>> Title:
>> juju should pool connections to mongo
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/juju/+bug/1786258/+subscriptions
>>
>
>