|
| 1 | +.. _4.4.25-changelog: |
| 2 | + |
| 3 | +4.4.25 Changelog |
| 4 | +---------------- |
| 5 | + |
| 6 | +Operations |
| 7 | +~~~~~~~~~~ |
| 8 | + |
| 9 | +- :issue:`SERVER-58534` Collect FCV in FTDC |
| 10 | +- :issue:`SERVER-77610` Log session id associated with the backup cursor |
| 11 | + |
| 12 | +Internals |
| 13 | +~~~~~~~~~ |
| 14 | + |
| 15 | +- :issue:`SERVER-52452` Enable feature flag for Make taking self-managed |
| 16 | + backups in 4.4+ as safe as possible |
| 17 | +- :issue:`SERVER-68132` Remove Feature Flag for PM-2076 |
| 18 | +- :issue:`SERVER-70973` Balancer should stop iterating collections when |
| 19 | + there are no more available shards |
| 20 | +- :issue:`SERVER-71627` Refreshed cached collection route info will |
| 21 | + severely block all client request when a cluster with 1 million chunks |
| 22 | +- :issue:`SERVER-73394` Remove misleading operationsBlockedByRefresh |
| 23 | + metrics |
| 24 | +- :issue:`SERVER-75255` Remove all outdated entries from |
| 25 | + backports_required_for_multiversion_tests.yml |
| 26 | +- :issue:`SERVER-78149` Implement the mongos fsync (lock : true) command |
| 27 | +- :issue:`SERVER-78150` Implement the mongos fsyncUnlock command |
| 28 | +- :issue:`SERVER-78151` Add fsyncLock status to the mongos currentOp |
| 29 | + command |
| 30 | +- :issue:`SERVER-78153` Unlock the config server primary via the mongos |
| 31 | + fsyncUnlock command |
| 32 | +- :issue:`SERVER-78156` Test the mongos fsync with lock command with |
| 33 | + distributed transactions |
| 34 | +- :issue:`SERVER-78793` Add a timeout to the mongos FSync Lock Command |
| 35 | +- :issue:`SERVER-78813` Commit point propagation fails indefinitely with |
| 36 | + exhaust cursors with null lastCommitted optime |
| 37 | +- :issue:`SERVER-78987` Remove the free monitoring code from |
| 38 | + mongodb/mongo repo |
| 39 | +- :issue:`SERVER-79025` Mongos Fsync with lock command should use mongos |
| 40 | + fsyncUnlock command |
| 41 | +- :issue:`SERVER-79127` Error when $vectorSearch limit is <= 0 |
| 42 | +- :issue:`SERVER-79252` Add the system-perf bootstrap file to the task |
| 43 | + Files section |
| 44 | +- :issue:`SERVER-79885` Oplog fetching getMore should not set null |
| 45 | + lastKnownCommittedOpTime if it is not using exhaust cursors |
| 46 | +- :issue:`SERVER-80140` Use the $currentOp to verify that |
| 47 | + fsyncLockWorker threads are waiting for the lock |
| 48 | +- :issue:`SERVER-80488` Avoid traversing routing table in balancer split |
| 49 | + chunk policy |
| 50 | +- :issue:`SERVER-80491` Expose more granular metrics around balancing |
| 51 | + round |
| 52 | +- :issue:`SERVER-80499` Fix use-after-free in planShardedSearch |
| 53 | +- :issue:`SERVER-80544` Fix incorrect wait in |
| 54 | + runSearchCommandWithRetries |
| 55 | +- :issue:`SERVER-80678` Remove an outdated test case |
| 56 | +- :issue:`SERVER-80694` [v4.4] FCV gate null lastKnownCommittedOpTime |
| 57 | + behavior in oplog getMore |
| 58 | +- :issue:`SERVER-80703` Avoid traversing routing table in |
| 59 | + MigrationDestinationManager |
| 60 | +- :issue:`WT-8157` Fix format-abort-recovery-stress-test timeout |
| 61 | + condition |
| 62 | +- :issue:`WT-8570` Do not increase oldest ID during recovery |
| 63 | +- :issue:`WT-8614` Make format.sh more verbose for failure diagnosis |
| 64 | +- :issue:`WT-8702` Limit oldest id to recovered checkpoint snapshot in |
| 65 | + recovery |
| 66 | +- :issue:`WT-8709` RTS: Do not hold the oldest id of logged tables. |
| 67 | +- :issue:`WT-8825` Fix test_checkpoint_snapshot05 expected value |
| 68 | + validation failure |
| 69 | +- :issue:`WT-9248` Fix test_checkpoint_snapshot05 failure and convert |
| 70 | + python tests to use stats logic wait |
| 71 | +- :issue:`WT-10449` Do not save update chain when there are no updates |
| 72 | + to be written to the history store |
| 73 | +- :issue:`WT-10522` Fix a bug that leads to an unexpected aborted |
| 74 | + tombstone on update chain |
| 75 | +- :issue:`WT-11374` Fix comparison of txnid to timestamp in row_modify |
| 76 | + (v5.0) |
| 77 | +- :issue:`WT-11492` Assertion fires in test_checkpoint_snapshot05 on |
| 78 | + windows-64 |
| 79 | + |
0 commit comments