MongoDB Node.js driver 2.2.23 released

[Christian Kvalheim]

Node 2.2.23 fixes an issue where batch scripts would schedule a lot of long running aggregations in parallel and experiencing that they would be pipelined on the same connection. The change grows the pool aggressively until maxPoolSize before starting scheduling if there are no free connections when a new operation is executed. This ensures long running aggregations get distributed across multiple connections from the start avoiding pipelining until there the poolSize < maxPoolSize.

Furthermore there was a fix for normalizing host names where users mixed hosts names with uppercase and lowercase in the seedlist and replicaset configuration.

Finally we fixed a small regression where auth was being performed against arbiters and where sometimes the MongoClient would not close down correctly because the last pipelined operation would never execute.

2.2.23 2017-02-13
-----------------
* Updated mongodb-core to 2.1.8.
* NODE-925 ensure we reschedule operations while pool is < poolSize while pool is growing and there are no connections with not currently performing work.
* NODE-927 fixes issue where authentication was performed against arbiter instances.
* NODE-915 Normalize all host names to avoid comparison issues.
* Fixed issue where pool.destroy would never finish due to a single operation not being executed and keeping it open.
* NODE-931 Validates all the options for MongoClient.connect and fixes missing connection settings.
* NODE-929 Update SSL tutorial to correctly reflect the non-need for server/mongos/replset subobjects
* Fix sensitive command check (Issue #1473, https://github.com/Annoraaq)