[SERVER-46103] Retain NonResumableChangeStreamError label for 4.4 Created: 12/Feb/20  Updated: 29/Oct/23  Resolved: 21/Feb/20

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Bernard Gorman
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-46104 Remove NonResumableChangeStreamError ... Backlog
is related to SERVER-45505 Add ResumableChangeStreamError error ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-02-24
Participants:

 Description   

After speaking with jeff.yemin, we are concerned that with the removal of the NonResumableChangeStreamError label in SERVER-45505, older drivers running on a 4.4 deployment would be exposed to all the driver retry loop scenarios that we have previously addressed. As such, we should continue to attach the NonResumableChangeStreamError label to command responses in 4.4. New drivers will obey the ResumableChangeStreamError whitelist, while older drivers will obey the NonResumableChangeStreamError blacklist.

While this will safeguard older drivers against all known cases where a driver retry loop is possible, we will not commit to maintaining the blacklist going forward, and will remove it in a future release.

cc divjot.arora



 Comments   
Comment by Githook User [ 21/Feb/20 ]

Author:

{'name': 'Bernard Gorman', 'username': 'gormanb', 'email': 'bernard.gorman@gmail.com'}

Message: SERVER-46103 Retain NonResumableChangeStreamError label for 4.4
Branch: master
https://github.com/mongodb/mongo/commit/9bd2f484cb48136bb29c7eb7e0fc0ca34038fe3b

Generated at Thu Feb 08 05:10:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.