[SERVER-69244] $merge fails when session default read concern has been set to "majority" Created: 30/Aug/22 Updated: 30/Oct/23 Resolved: 05/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.11, 7.0.3, 6.0.12, 7.0.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jess Balint | Assignee: | Jess Balint |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | auto-reverted | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v7.0, v6.0, v5.0, v4.4
|
||||||||||||||||||||
| Sprint: | QO 2022-08-22, QO 2022-09-19, QO 2022-10-03, QE 2022-10-17 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Linked BF Score: | 162 | ||||||||||||||||||||
| Description |
| Comments |
| Comment by Githook User [ 27/Oct/23 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jess.balint@mongodb.com', 'username': ''}Message: (cherry picked from commit 46b37b276a0d73f583ba2cee92175cb9156c028f) |
| Comment by Githook User [ 26/Oct/23 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jess.balint@mongodb.com', 'username': ''}Message: (cherry picked from commit 46fbe5b380dfaa32ee22b137162d90db9debd23e) |
| Comment by Githook User [ 22/Sep/23 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jess.balint@mongodb.com', 'username': ''}Message: (cherry picked from commit 46fbe5b380dfaa32ee22b137162d90db9debd23e) |
| Comment by Steve Tarzia [ 13/Sep/23 ] |
|
Yes, we should still do these, but we haven't started yet. Thanks for the reminder, garaudy.etienne@mongodb.com! We'll get a sense of the difficulty when we start moving backward through the versions. |
| Comment by Garaudy Etienne [ 13/Sep/23 ] |
|
do we still plan on doing these backports? are they trivial? |
| Comment by Jess Balint [ 05/May/23 ] |
|
The workaround is to avoid setting the default read concern. |
| Comment by Arun Kant [ 05/May/23 ] |
|
Is there a workaround to address this issue ? We are seeing this issue with mongo 6.x enterprise version when using $merge ? We need this feature to populate another collection based from data in source collection. Source collection is sharded collection and target collection is not a sharded collection. Please advise. |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jbalint@gmail.com', 'username': 'jbalint'}Message: |
| Comment by xgen-buildbaron-user [ 19/Apr/23 ] |
|
Ticket re-opened due to revert. sharding_multiversion began a consistent failure of jstests/sharding/query/merge_nondefault_read_concern.js |
| Comment by Githook User [ 19/Apr/23 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 2147b61844e1783f003ae5c42bee846f85b79105. |
| Comment by Githook User [ 18/Apr/23 ] |
|
Author: {'name': 'Jess Balint', 'email': 'jbalint@gmail.com', 'username': 'jbalint'}Message: |