MongoDB Documentation, Release 3.0.4 Testing SERVER-16421 $^{356}$sharding_rs2.js should clean up data on all replicas $^{356}$https://jira.mongodb.org/browse/SERVER-16421 $^{357}$https://jira.mongodb.org/browse/SERVER-16237 $^{358}$https://jira.mongodb.org/browse/SERVER-16408 $^{359}$https://jira.mongodb.org/browse/SERVER-16732 $^{360}$https://jira.mongodb.org/browse/SERVER-16683 $^{361}$https://jira.mongodb.org/browse/SERVER-15766 $^{362}$https://jira.mongodb.org/browse/SERVER-14306 $^{363}$https://jira.mongodb.org/browse/SERVER-16081 $^{364}$https://jira.mongodb.org/browse/SERVER-15673 $^{366}$https://jira.mongodb.org/browse/SERVER-15500 $^{365}$https://jira.mongodb.org/browse/SERVER-15515 Chapter 12. Release Notes 832 • SERVER-16237 357 Don’t check the shard version if the primary server is down • SERVER-16732 359 SyncSourceFeedback::replHandshake() may perform an illegal erase from a std::map in some circumstances • SERVER-16408 358 max_time_ms.js should not run in parallel suite. • SERVER-16683 360 Decrease mongos memory footprint when shards have several tags • SERVER-15766 361 prefix_shard_key.js depends on primary allocation to particular shards • SERVER-14306 362 mongos can cause shards to hit the in-memory sort limit by requesting more results than needed. • SERVER-16081 363 /etc/init.d/mongod startup script fails, with dirname message • SERVER-15673 364 Disable SSLv3 ciphers • SERVER-15515 365 New test for mixed version replSet, 2.4 primary, user updates • SERVER-15500 366 New test for system.user operations 2.6.6 – Changes Security Packaging Sharding Replication Querying Stability 2.6.7 – Changes