## Geospatial 

• SERVER-13666 600 $near queries with out-of-bounds points in legacy format can lead to crashes 

• SERVER-13540 601 The geoNear command no longer returns distance in radians for legacy point 

• SERVER-13486$^{602}$: The geoNear command can create too large BSON objects for aggregation. 

## Replication 

• SERVER-13500 603 Changing replica set configuration can crash running members 

• SERVER-13589 604 Background index builds from a 2.6.0 primary fail to complete on 2.4.x secondaries 

• SERVER-13620 605 Replicated data definition commands will fail on secondaries during background index build 

• SERVER-13496 606 Creating index with same name but different spec in mixed version replicaset can abort replication 

## Sharding 

• SERVER-12638 607 Initial sharding with hashed shard key can result in duplicate split points 

• SERVER-13518 608 The _id field is no longer automatically generated by mongos when missing 

• SERVER-13777 609 Migrated ranges waiting for deletion do not report cursors still open 

## Security 

• SERVER-9358 610 Log rotation can overwrite previous log files 

• SERVER-13644 611 Sensitive credentials in startup options are not redacted and may be exposed 

• SERVER-13441 612 Inconsistent error handling in user management shell helpers 

## Write Operations 

• SERVER-13466 613 Error message in collection creation failure contains incorrect namespace 

• SERVER-13499 614 Yield policy for batch-inserts should be the same as for batch-updates/deletes 

• SERVER-13516 615 Array updates on documents with more than 128 BSON elements may crash mongod 

