[SERVER-65497] Server Error when using a new structure in ns document Created: 12/Apr/22 Updated: 29/Oct/23 Resolved: 22/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc2, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steve Silvester | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v6.0, v5.3
|
||||||||||||||||||||||||
| Sprint: | QE 2022-04-18, QE 2022-05-02 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
As part of DRIVERS-1995 there is a specification test called Test new structure in ns document MUST NOT err. The test passes the Python Driver for all cases except when a sharded cluster is used in the latest and rapid releases. I verified this locally by:
|
| Comments |
| Comment by Shane Harvey [ 09/May/22 ] | ||
|
Ignore my request. DBX is just going to skip testing this case on 5.3 after the changes on https://github.com/mongodb/specifications/pull/1209. | ||
| Comment by Kyle Suarez [ 08/May/22 ] | ||
|
shane.harvey@mongodb.com – we could backport to 5.3, but with 6.0 coming out so soon afterwards it may not even matter. In any case, I filed a backport request for the Query Execution team to discuss at the next triage meeting. | ||
| Comment by Shane Harvey [ 05/May/22 ] | ||
|
Does this fix need to be backported to 5.3 too? | ||
| Comment by Githook User [ 23/Apr/22 ] | ||
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: (cherry picked from commit c7b46ffe630f5e323d834d6278330336bbbde32c) | ||
| Comment by Githook User [ 22/Apr/22 ] | ||
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: | ||
| Comment by Kyle Suarez [ 12/Apr/22 ] | ||
|
Marking this as "6.0 Required" but also just "P3 - Major", as I think it's fine for us to target 6.0.0-rc1. I don't think there's any need for us to delay rc0 any further. | ||
| Comment by Steve Silvester [ 12/Apr/22 ] | ||
| ||
| Comment by Kyle Suarez [ 12/Apr/22 ] | ||
|
bernard.gorman@mongodb.com is investigating this and can reproduce the issue locally. We're going to prioritize fixing this bug as part of PM-1950, which introduced many $changeStream changes for the 6.0 release. | ||
| Comment by Kyle Suarez [ 12/Apr/22 ] | ||
|
steve.silvester@mongodb.com, do you have the logs of the servers from when this error occurred? |