SINGLE MODE

       In single mode, your program creates a mongoc_client_t directly:

          mongoc_client_t *client = mongoc_client_new (
             "mongodb://hostA,hostB/?replicaSet=my_rs");

       The client connects on demand when  your  program  first  uses  it  for  a  MongoDB  operation.  Using  a
       non-blocking  socket per server, it begins a check on each server concurrently, and uses the asynchronous
       poll or select function to receive events from the sockets, until all have responded or  timed  out.  Put
       another way, in single-threaded mode the C Driver fans out to begin all checks concurrently, then fans in
       once  all checks have completed or timed out. Once the scan completes, the client executes your program's
       operation and returns.

       In single mode, the client re-scans the server topology roughly once per minute. If more  than  a  minute
       has  elapsed  since  the  previous  scan,  the  next  operation on the client will block while the client
       completes its scan. This interval is configurable with heartbeatFrequencyMS  in  the  connection  string.
       (See mongoc_uri_t.)

       A  single  client  opens  one connection per server in your topology: these connections are used both for
       scanning the topology and performing normal operations.

POOLED MODE

       To activate pooled mode, create a mongoc_client_pool_t:

          mongoc_uri_t *uri = mongoc_uri_new (
             "mongodb://hostA,hostB/?replicaSet=my_rs");

          mongoc_client_pool_t *pool = mongoc_client_pool_new (uri);

       When your program first calls mongoc_client_pool_pop(), the  pool  launches  monitoring  threads  in  the
       background.  Monitoring  threads  independently  connect  to  all  servers  in  the connection string. As
       monitoring threads receive hello responses from the servers, they update the shared view  of  the  server
       topology.  Additional  monitoring  threads  and  connections  are  created as new servers are discovered.
       Monitoring threads are terminated when servers are removed from the shared view of the server topology.

       Each thread that executes MongoDB operations must check out a client from the pool:

          mongoc_client_t *client = mongoc_client_pool_pop (pool);

          /* use the client for operations ... */

          mongoc_client_pool_push (pool, client);

       The mongoc_client_t object is not thread-safe, only the mongoc_client_pool_t is.

       When the driver is in pooled mode,  your  program's  operations  are  unblocked  as  soon  as  monitoring
       discovers  a usable server. For example, if a thread in your program is waiting to execute an "insert" on
       the primary, it is unblocked as  soon  as  the  primary  is  discovered,  rather  than  waiting  for  all
       secondaries to be checked as well.

       The pool opens one connection per server for monitoring, and each client opens its own connection to each
       server  it  uses  for application operations. Background monitoring threads re-scan servers independently
       roughly every 10 seconds. This interval is  configurable  with  heartbeatFrequencyMS  in  the  connection
       string. (See mongoc_uri_t.)

       The connection string can also specify waitQueueTimeoutMS to limit the time that mongoc_client_pool_pop()
       will  wait  for a client from the pool.  (See mongoc_uri_t.)  If waitQueueTimeoutMS is specified, then it
       is necessary to confirm that a client was actually returned:

          mongoc_uri_t *uri = mongoc_uri_new (
             "mongodb://hostA,hostB/?replicaSet=my_rs&waitQueueTimeoutMS=1000");

          mongoc_client_pool_t *pool = mongoc_client_pool_new (uri);

          mongoc_client_t *client = mongoc_client_pool_pop (pool);

          if (client) {
             /* use the client for operations ... */

             mongoc_client_pool_push (pool, client);
          } else {
             /* take appropriate action for a timeout */
          }

       See Connection Pool Options to configure pool size and behavior,  and  see  mongoc_client_pool_t  for  an
       extended example of a multi-threaded program that uses the driver in pooled mode.

AUTHOR

       MongoDB, Inc

COPYRIGHT

       2017-present, MongoDB, Inc

1.26.0                                            Mar 31, 2024                      MONGOC_CONNECTION_POOLING(3)