|
| 1 | +.. _5.0.10-changelog: |
| 2 | + |
| 3 | +5.0.10 Changelog |
| 4 | +---------------- |
| 5 | + |
| 6 | +Sharding |
| 7 | +~~~~~~~~ |
| 8 | + |
| 9 | +- :issue:`SERVER-56185` Investigate possible improvements with session migration and a chunk migration's critical section |
| 10 | +- :issue:`SERVER-57519` Make ARS use causally consistent ShardRegistry::getShard() function |
| 11 | +- :issue:`SERVER-61985` resharding_coordinator_recovers_abort_decision.js may report resharding operation as succeeding due to primary shard retrying _configsvrReshardCollection and running a second resharding operation |
| 12 | +- :issue:`SERVER-62272` Adding schema validation to a collection can prevent chunk migrations of failing documents |
| 13 | +- :issue:`SERVER-62656` Decouple mongos-to-config-server connection pool sizing from mongos-to-shard-server connection pool sizing |
| 14 | +- :issue:`SERVER-63243` Range deleter must not clean up orphan ranges in a round-robin fashion |
| 15 | +- :issue:`SERVER-64433` A new topology time could be gossiped without being majority committed |
| 16 | +- :issue:`SERVER-65027` Resharding commands permit extra options without returning an error |
| 17 | +- :issue:`SERVER-65821` Deadlock during setFCV when there are prepared transactions that have not persisted commit/abort decision |
| 18 | +- :issue:`SERVER-65925` shardsvrCommitReshardCollection should check for transient errors when joining |
| 19 | +- :issue:`SERVER-65930` DDL coordinators and rename participant initial checkpoint may incur in DuplicateKey error |
| 20 | +- :issue:`SERVER-66046` Resharding coordinator won't automatically abort the resharding operation when a recipient shard errors during its applying phase |
| 21 | +- :issue:`SERVER-66618` Ensure ReshardingCoordinator has aborted in resharding_coordinator_recovers_abort_decision.js |
| 22 | +- :issue:`SERVER-66866` The range deleter waits between batches while holding the collection IX lock |
| 23 | +- :issue:`SERVER-67457` Resharding operation aborted in the midst of contacting participants may stall on config server primary indefinitely |
| 24 | + |
| 25 | +JavaScript |
| 26 | +~~~~~~~~~~ |
| 27 | + |
| 28 | +:issue:`SERVER-61234` JS object-based types are not properly auto-serialized when directly returned by server-side JS functions |
| 29 | + |
| 30 | +Build and Packaging |
| 31 | +~~~~~~~~~~~~~~~~~~~ |
| 32 | + |
| 33 | +- :issue:`SERVER-61894` Support the 'showRawUpdateDescription' option in change stream specs |
| 34 | +- :issue:`SERVER-63159` Implement the $_internalApplyOplogUpdate aggregation stage |
| 35 | +- :issue:`SERVER-66627` Backport the install-devcore target |
| 36 | + |
| 37 | +Internals |
| 38 | +~~~~~~~~~ |
| 39 | + |
| 40 | +- :issue:`SERVER-57938` Skip polygon validation for stored GeoJSON when query has $geoIntersect and a 2dsphere index |
| 41 | +- :issue:`SERVER-58257` Add better diagnostics to predictive_connpool.js |
| 42 | +- :issue:`SERVER-59658` Improve logging to reflect that sharding metadata refresh waiting on replication |
| 43 | +- :issue:`SERVER-61856` Upgrade libunwind to 1.6.2+ |
| 44 | +- :issue:`SERVER-62386` Coverity analysis defect 121298: Parse warning |
| 45 | +- :issue:`SERVER-62716` Handle spurious finishWaitingForOneOpTime in WaitForMajorityServiceTest |
| 46 | +- :issue:`SERVER-63271` serverStatus can fail the server |
| 47 | +- :issue:`SERVER-63493` update-shard-key tests failing due to transaction lock timeouts |
| 48 | +- :issue:`SERVER-63971` Change server parameter to default to read-your-writes behavior after 2PC transaction |
| 49 | +- :issue:`SERVER-64215` Interrupt OplogBufferMock::waitForData on shutdown |
| 50 | +- :issue:`SERVER-64244` RunDBCheckInBackground should be resilient to interrupts |
| 51 | +- :issue:`SERVER-64509` Fix ShardRegistry threadpool shutdown order |
| 52 | +- :issue:`SERVER-64627` Need general method to handle in-memory state after initial sync |
| 53 | +- :issue:`SERVER-64628` More testing of adding nodes to sharded sets |
| 54 | +- :issue:`SERVER-64659` Report in serverStatus number of file descriptors used during index builds |
| 55 | +- :issue:`SERVER-64725` Make ShardRegistry::periodicReloader interruptible |
| 56 | +- :issue:`SERVER-64797` Use WT's new numerical timestamp API |
| 57 | +- :issue:`SERVER-65100` Increase memory block size for BSONColumn |
| 58 | +- :issue:`SERVER-65131` Disable opportunistic read targeting (except for hedged reads) |
| 59 | +- :issue:`SERVER-65313` Use BatchedCollectionCatalogWriter during startup recovery |
| 60 | +- :issue:`SERVER-65371` MigrationSourceManager running on secondary node may trip invariant |
| 61 | +- :issue:`SERVER-65399` 'commitIndexBuild' oplog entry is a no-op for unfinished index builds not restarted |
| 62 | +- :issue:`SERVER-65723` Add tunable parameter to improve batching on secondaries |
| 63 | +- :issue:`SERVER-65777` "revokePrivilegesFromRole" param.ns missing user object in audit log |
| 64 | +- :issue:`SERVER-65797` Remove invalid index specs in memory before parsing for listIndexes |
| 65 | +- :issue:`SERVER-65884` $lookup from time-series can place $sequentialCache after correlated $match |
| 66 | +- :issue:`SERVER-66087` Call curl_global_init before threading enabled |
| 67 | +- :issue:`SERVER-66111` Curl implementation of HTTPClient should respect default timeouts |
| 68 | +- :issue:`SERVER-66319` dbcheck_no_history_on_secondary.js disables dbCheck failpoint too early |
| 69 | +- :issue:`SERVER-66379` $or to $in conversion flawed |
| 70 | +- :issue:`SERVER-66384` Enable command line customization of NINJA_BUILDDIR |
| 71 | +- :issue:`SERVER-66418` Bad projection created during dependency analysis due to string order assumption |
| 72 | +- :issue:`SERVER-66433` Backport deadline waiting for overlapping range deletion to finish to pre-v5.1 versions |
| 73 | +- :issue:`SERVER-66461` Run notarization earlier in the build process |
| 74 | +- :issue:`SERVER-66520` add index build UUID to BackgroundOperationInProgress error messages |
| 75 | +- :issue:`SERVER-66548` $lookup sequential cache can incorrectly treat a $facet as non-correlated |
| 76 | +- :issue:`SERVER-66556` Prevent potential race when releasing cursors during shutdown |
| 77 | +- :issue:`SERVER-66559` Expand the internalQueryMaxAddToSetBytes param from 32 to 64 bits |
| 78 | +- :issue:`SERVER-66658` Shard registry might be accessed before initialization |
| 79 | +- :issue:`SERVER-66727` Time-series bucket can be created that violates max time-span |
| 80 | +- :issue:`SERVER-66769` Update spawnhost setup script to support Windows hosts via cygwin |
| 81 | +- :issue:`SERVER-66799` Fix getParameterWithDetails.js failure on ephemeralForTest |
| 82 | +- :issue:`SERVER-66843` Use defensive programming in DeadlineFuture destructor |
| 83 | +- :issue:`SERVER-66860` FSM tests should not reuse same database names |
| 84 | +- :issue:`SERVER-66902` Multiversion setup is consistently failing on the mongodb-mongo-v5.0 Evergreen project |
| 85 | +- :issue:`SERVER-66955` Remove JSON.send usage in perf projects |
| 86 | +- :issue:`SERVER-67014` Say that "the client driver may require an upgrade" in warning message for deprecated op codes in 5.0 |
| 87 | +- :issue:`SERVER-67106` The _flushRoutingTableCacheUpdates() command should be able to also serve requests referencing collection views. |
| 88 | +- :issue:`SERVER-67167` DIsable or_to_in.js from running in the parallel suite |
| 89 | +- :issue:`SERVER-67220` [5.0] set_fcv_prepared_transaction.js is not resilient to StaleConfig errors |
| 90 | +- :issue:`SERVER-67405` Handle empty string for is_patch evergreen expansion |
| 91 | +- :issue:`SERVER-67513` Disable or_to_in for jsCore_compatibility for v5.0 |
| 92 | +- :issue:`SERVER-68193` Sharding DDL coordinator can lock itself out in distlock retry loop |
| 93 | +- :issue:`WT-8425` Push updates with the same commit timestamps in the out_of_order_ts_updates vector in hs_rec.c. |
| 94 | +- :issue:`WT-8669` Assert that the timestamps are not OOO in __hs_insert_record |
| 95 | +- :issue:`WT-9249` Compare and fix the start durable timestamp if it is greater than ooo timestamp |
| 96 | +- :issue:`WT-9251` Perform log flush before the metadata checkpoint |
| 97 | + |
0 commit comments