Skip to content

Commit 7f6d9a0

Browse files
authored
DOCS-15017 add 5.0.6 release notes (#250)
1 parent 4a241cd commit 7f6d9a0

File tree

3 files changed

+142
-0
lines changed

3 files changed

+142
-0
lines changed
Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
.. _5.0.6-changelog:
2+
3+
5.0.6 Changelog
4+
---------------
5+
6+
Sharding
7+
~~~~~~~~
8+
9+
- :issue:`SERVER-45149` replSetStepDown command in txn_two_phase_commit_failover.js should not timeout
10+
- :issue:`SERVER-56127` Retryable update may execute more than once if chunk is migrated and shard key pattern uses nested fields
11+
- :issue:`SERVER-56227` Add user-facing command to set allowMigrations to false for a sharded collection
12+
- :issue:`SERVER-60624` txn_commit_optimizations_for_read_only_shards.js pauses replication on coordinator and can leave transaction stuck in prepare
13+
- :issue:`SERVER-60682` TransactionCoordinator may block acquiring WiredTiger write ticket to persist its decision, prolonging transactions being in the prepared state
14+
- :issue:`SERVER-60860` ReshardingCollectionCloner uses primary read preference when nearest was intended
15+
- :issue:`SERVER-61003` ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried
16+
- :issue:`SERVER-61105` The sessions migration logic during moveChunk pollutes the logs
17+
- :issue:`SERVER-61268` Fixing the release of a recoverable critical section on secondaries
18+
- :issue:`SERVER-61416` Indefinitely retry errors in rename coordinator
19+
- :issue:`SERVER-61459` ShardingCatalogManager::assignKeyRangeToZone() reads stale version of CollectionType while running locally on config server primary
20+
- :issue:`SERVER-61461` update_shard_key_doc_moves_shards.js fails due to spurious refreshes from secondaries
21+
- :issue:`SERVER-61628` Do not reschedule range deletion task when numDeleted < numDocsToRemovePerBatch
22+
- :issue:`SERVER-61637` Review range deleter batching policy
23+
- :issue:`SERVER-61689` ActiveMigrationsRegistry::lock method doesn't properly handle its exceptions
24+
- :issue:`SERVER-61759` Unsetting the AllowMigrations flag should abort ongoing migrations
25+
- :issue:`SERVER-61816` cancel_coordinate_txn_commit_with_tickets_exhausted.js can hang forever due to race condition between transaction reaper and transaction coordinator
26+
- :issue:`SERVER-61945` Resharding collection cloning may fail with NamespaceNotSharded when "nearest" read preference chooses secondary
27+
- :issue:`SERVER-61950` ReshardingOplogFetcher waits on network request completing without interruption, potentially preventing shard step-up from ever completing
28+
- :issue:`SERVER-62207` ReshardCollection with small maxTimeMS can crash the shard due to incorrect BSON object lifetime
29+
- :issue:`SERVER-62245` MigrationRecovery must not assume that only one migration needs to be recovered
30+
- :issue:`SERVER-62296` MoveChunk should recover any unfinished migration before starting a new one
31+
32+
Replication
33+
~~~~~~~~~~~
34+
35+
:issue:`SERVER-59721` Node may become unable to sync from other members after performing rollback to stable timestamp
36+
37+
Query
38+
~~~~~
39+
40+
:issue:`SERVER-57588` Inconsistent query results when an array position is indexed whose value is an array
41+
42+
Storage
43+
~~~~~~~
44+
45+
- :issue:`SERVER-30846` Run dbCheck as background workload in FSM tests
46+
- :issue:`SERVER-55483` Add a new startup parameter that skips verifying the table log settings
47+
- :issue:`SERVER-58409` Startup RecordId initialization is flawed with durable history and reconstructing prepared transactions
48+
49+
Operations
50+
~~~~~~~~~~
51+
52+
:issue:`SERVER-28953` Capture df (disk full) statistics in FTDC
53+
54+
Internals
55+
~~~~~~~~~
56+
57+
- :issue:`SERVER-49748` Initial sync should clone admin.system.version before any other collections
58+
- :issue:`SERVER-54468` Enable Feature flag for Minimal support for sharding time-series collections
59+
- :issue:`SERVER-56167` Guarantee hang analyzer collects core dumps for sharded clusters, at minimum
60+
- :issue:`SERVER-57037` Improve precision of operator counters
61+
- :issue:`SERVER-57289` redact should not convert BSONArray into BSONObj
62+
- :issue:`SERVER-57312` Pin transitive Python dependencies and use the pinned file for installation in Evergreen
63+
- :issue:`SERVER-57772` Failpoints on mongos rewrite state change error codes in writeConcernError
64+
- :issue:`SERVER-58135` ReplSetTest initiate failing in replica sets with chaining disabled
65+
- :issue:`SERVER-59428` Use more robust regex matching in rollback resumable index build fixture
66+
- :issue:`SERVER-59781` multi_statement_transaction.js does not retry transaction on StaleConfig
67+
- :issue:`SERVER-60217` [v5.0] enableReconfigRollbackCommittedWritesCheck should be applied on 4.4
68+
- :issue:`SERVER-60310` OCSP response validation should not consider statuses of irrelevant certificates
69+
- :issue:`SERVER-60334` Pause the WiredTigerSizeStorer during Rollback To Stable
70+
- :issue:`SERVER-60513` Run burn_in_tags compile on -large distro
71+
- :issue:`SERVER-60517` Enforce eviction_dirty_target < eviction_dirty_trigger in the fuzzer
72+
- :issue:`SERVER-60685` TransactionCoordinator may interrupt locally executing update with non-Interruption error category, leading to server crash
73+
- :issue:`SERVER-60788` merge_causes_infinite_loop.js attempts to expose a problem that no longer exists
74+
- :issue:`SERVER-60809` Add ability to not idLookup after $search
75+
- :issue:`SERVER-61005` rs.initiate() fails with "Invariant failure" under specific startup options
76+
- :issue:`SERVER-61012` Instantiation of TEMPLATE rule sometimes has a command in generated ninja
77+
- :issue:`SERVER-61097` SizeStorer can cause deadlocks with cache eviction
78+
- :issue:`SERVER-61188` When storeImageInSideCollection=true, pre-image noop entries for collection with preImageRecordingEnabledForCollection=true are assigned wrong opTimes
79+
- :issue:`SERVER-61194` Prevent time-series bucket OID reuse with coarse granularity
80+
- :issue:`SERVER-61201` Creating a view can lead to a deadlock
81+
- :issue:`SERVER-61214` Ensure having the latest known entry of the catalog cache when creating config.system.sessions
82+
- :issue:`SERVER-61216` The --cache-disable flag results in a python stacktrace
83+
- :issue:`SERVER-61275` Destruct the size storer after the session cache has shutdown
84+
- :issue:`SERVER-61358` validate cachedir incorrectly re-raising InvalidChecksum
85+
- :issue:`SERVER-61427` Unique index builds can cause a loss of availability during commit due to checking many false duplicates
86+
- :issue:`SERVER-61479` Increase the number of retries to connect to a replica set following a stepdown
87+
- :issue:`SERVER-61532` Opcounters to detect constrain violations need to be exposed.
88+
- :issue:`SERVER-61550` Modify auto_workload_path in perf.yml to be relative to cwd
89+
- :issue:`SERVER-61591` Robustify currentop_shell.js test
90+
- :issue:`SERVER-61602` timeseries_min_max.js assumes measurements are returned in insertion order
91+
- :issue:`SERVER-61650` Disconnect nodes before restarting replication in sync_source_selection_ignores_minvalid_after_rollback.js
92+
- :issue:`SERVER-61681` Wait for replSetGetStatus to update in replSetGetStatus_member_wall_times.js
93+
- :issue:`SERVER-61690` Adjust stored fields protocol for atlas search
94+
- :issue:`SERVER-61738` Revive dbCheck.js and make it deterministic
95+
- :issue:`SERVER-61743` The -fno-builtin-memcmp flag shouldn't be applied except on x86_64 platforms
96+
- :issue:`SERVER-61748` dbCheck should not hold a strong database lock during batches
97+
- :issue:`SERVER-61754` dbCheck should not hold a strong collection lock during batches
98+
- :issue:`SERVER-61757` Add a dbCheck command option to customize the batch size
99+
- :issue:`SERVER-61791` pin pymongo
100+
- :issue:`SERVER-61805` Use port to check primary node in timeseries_retryable_write_downgrade_oplog_rollover.js
101+
- :issue:`SERVER-61846` Prevent redact from throwing BSONObjectTooLarge
102+
- :issue:`SERVER-61852` dbCheck should tryLock the collection with backoff
103+
- :issue:`SERVER-61858` Wait for node to become primary before disconnecting in sync_source_selection_ignores_minvalid_after_rollback.js
104+
- :issue:`SERVER-61877` Remove catalog consistency verification from dbCheck
105+
- :issue:`SERVER-61883` [v5.0] Read support for compressed time-series buckets
106+
- :issue:`SERVER-61910` initiate_takes_stable_checkpoint.js doesn't account for closing connections in rollback
107+
- :issue:`SERVER-61931` Allow ClusterManager role to operate against system.buckets.* collections
108+
- :issue:`SERVER-61955` Expose dbCheck as a generally available command
109+
- :issue:`SERVER-62022` Reduce dbCheck info logging in production, log start and stop
110+
- :issue:`SERVER-62023` Improve dbCheck observability
111+
- :issue:`SERVER-62037` Fix replica set definition in the system perf yaml file for linux-1-node-15gbwtcache
112+
- :issue:`SERVER-62041` Add a maximum batch execution time to dbCheck
113+
- :issue:`SERVER-62164` Remove several obsoleted build variants across all stable branches
114+
- :issue:`SERVER-62210` Fix dbCheck progress meter handling of dropped and recreated collections
115+
- :issue:`SERVER-62212` Support writeConcern for dbCheck
116+
- :issue:`SERVER-62226` Disable dbcheck_no_history_on_secondary.js on EFT
117+
- :issue:`SERVER-62243` Wait for vector clock document majority-commit without timeout
118+
- :issue:`SERVER-62382` Several Amazon Linux 2 tests on the 5.0, 5.1, 5.2 and master waterfalls are not running
119+
- :issue:`WT-8395` Inconsistent data after upgrade from 4.4.3 and 4.4.4 to 4.4.8+ and 5.0.2+
120+
- :issue:`WT-8534` Allow retrieving checkpoint snapshot for backup restore recovery
121+
- :issue:`WT-8576` Enable logging in test checkpoint
122+

source/release-notes/5.0-changelog.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@
1010
:depth: 1
1111
:class: singlecol
1212

13+
.. include:: /includes/changelogs/releases/5.0.6.rst
14+
1315
.. include:: /includes/changelogs/releases/5.0.5.rst
1416

1517
.. include:: /includes/changelogs/releases/5.0.4.rst

source/release-notes/5.0.txt

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,24 @@ Release Notes for MongoDB 5.0
1717
Minor Releases
1818
--------------
1919

20+
.. _5.0.6-release-notes:
21+
22+
5.0.6 - Upcoming
23+
~~~~~~~~~~~~~~~~
24+
25+
Issues fixed:
26+
27+
- :issue:`WT-8395` Inconsistent data after upgrade from 4.4.3 and 4.4.4 to 4.4.8+ and 5.0.2+
28+
- :issue:`SERVER-62245` MigrationRecovery must not assume that only one migration needs to be recovered
29+
- :issue:`SERVER-61427` Unique index builds can cause a loss of availability during commit due to checking many false duplicates
30+
- :issue:`SERVER-61194` Prevent time-series bucket OID reuse with coarse granularity
31+
- :issue:`SERVER-60310` OCSP response validation should not consider statuses of irrelevant certificates
32+
33+
- `All JIRA issues closed in 5.0.6
34+
<https://jira.mongodb.org/issues/?jql=project%20in%20(SERVER%2C%20TOOLS%2C%20WT)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%205.0.6>`_
35+
36+
- :ref:`5.0.6-changelog`
37+
2038
.. _5.0.5-release-notes:
2139

2240
5.0.5 - December 6, 2021

0 commit comments

Comments
 (0)