[SERVER-57944] Targeter is not being clean completely after failed refresh on batch write executor Created: 22/Jun/21  Updated: 29/Oct/23  Resolved: 30/Jun/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.2, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-sprint
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-07-12
Participants:
Linked BF Score: 37

 Description   

If a database stale error is detected after a batch write round, there is an attempt to restart the targeter. However, if there is a failure while refreshing when getting the catalog cache (like for example, because of a drop database) then another batch write round will start, resending the operation to the shards, but, this time there is a possibility that one of the shards might've picked up the db version previously created by the router, which could lead to a shard stale error (the collection could've being recently dropped, as part of the aforementioned drop database) and this will cause a dassert to hit.

We could ensure that the targeter is refreshed after detecting a stale error, instead of ignoring it, or, we could ensure the current variable used to detect if the targeter was refreshed is being used properly.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 20/Jul/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-57944 Ensure stale state is cleared after a refresh attempt

... in the chunk manager targeter.

(cherry picked from commit c5ef3aea4f62f35ba5b7be7873a76fe2891e00b4)
Branch: v5.0
https://github.com/mongodb/mongo/commit/33aff9557db0e57b5edabe2d6e06b7dfd3f11c4f

Comment by Githook User [ 30/Jun/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-57944 Ensure stale state is cleared after a refresh attempt

... in the chunk manager targeter.
Branch: master
https://github.com/mongodb/mongo/commit/c5ef3aea4f62f35ba5b7be7873a76fe2891e00b4

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