Connection handling and persistence
Nota: Em plataformas Unix, o driver do MongoDB é sensível a scripts que usam a chamada de sistema fork() sem chamar também exec(). Os usuários são aconselhados a não reusar instâncias de MongoDB\Driver\Manager em um processo filho bifurcado.
Connection and topology persistence (PHP version since 1.2.0)
All versions of the driver since 1.2.0 persist the » libmongoc client object in the PHP worker process, which allows it to re-use database connections, authentication states, and topology information across multiple requests.
When MongoDB\Driver\Manager::__construct() is
invoked, a hash is created from its arguments (i.e. URI string and array
options). The driver will attempt to find a previously persisted
» libmongoc client object for
that hash. If an existing client cannot be found for the hash, a new client
will be created and persisted for future use. This behavior can be disabled
via the "disableClientPersistence" driver option.
Each client contains its own database connections and a view of the server topology (e.g. standalone, replica set, shard cluster). By persisting the client between PHP requests, the driver is able to re-use established database connections and remove the need for » discovering the server topology on each request.
Consider the following example:
<?php
$managers = [
new MongoDB\Driver\Manager('mongodb://127.0.0.1'),
new MongoDB\Driver\Manager('mongodb://127.0.0.1'),
new MongoDB\Driver\Manager('mongodb://127.0.0.1:27017'),
new MongoDB\Driver\Manager('mongodb://rs1.example.com,rs2.example.com/', ['replicaSet' => 'myReplicaSet']),
];
foreach ($managers as $manager) {
$manager->executeCommand('test', new MongoDB\Driver\Command(['ping' => 1]));
}
?>
The first two Manager objects will share the same
» libmongoc client since
their constructor arguments are identical. The third and fourth objects will
each use their own client. In total, three clients will be created and the
PHP worker executing this script will open two connections to
127.0.0.1 and one connection to each of
rs1.example.com and rs2.example.com.
If the driver discovers additional members of the replica set after issuing
hello commands, it will open additional connections to
those servers as well.
If the same worker executes the script again in a second request, the three
clients will be re-used and no new connections will be made. Depending on
how long ago the previous request was served, the driver may need to issue
additional hello commands to update its view of the
topologies.
Socket persistence (PHP versions before 1.2.0)
Versions of the PHP driver before 1.2.0 utilize PHP's Streams API for database connections, using an API within » libmongoc to designate custom handlers for socket communication; however, a new libmongoc client is created for each MongoDB\Driver\Manager. As a result, the driver persists individual database connections but not authentication state or topology information. This means that the driver needs to issue commands at the start of each request to authenticate and » discover the server topology.
Database connections are persisted by a hash derived from the server's host, port, and the URI string used to construct the MongoDB\Driver\Manager. The constructor's array options are not included in this hash.
Nota: Versions of the driver >= 1.1.8 and < 1.2.0 do not persist sockets for SSL connections. See » PHPC-720 for additional information.
Despite its shortcomings with persisting SSL connections when and topology information, this version of the driver supports all SSL context options since it uses PHP's Streams API.
add a note
