[SERVER-36232] Refresh after chunk migration commit may not see the committed metadata Created: 20/Jul/18  Updated: 29/Oct/23  Resolved: 23/Jul/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.16, 3.6.6, 4.0.0, 4.1.1
Fix Version/s: 3.4.17, 3.6.7, 4.0.1, 4.1.2

Type: Bug Priority: Critical - P2
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-36132 Invariant that chunk migration is act... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6, v3.4
Sprint: Sharding 2018-07-30
Participants:
Linked BF Score: 0

 Description   

The chunk migration logic uses the CatalogCache to refresh the metadata after issuing the commit against the config server. SERVER-33954 uncovered that the catalog cache's "WithRefresh" methods are not causally consistent and because of this, it is possible that a refresh after chunk migration commit could join a concurrent refresh and not see its own changes.

This should be backported together with SERVER-36132.



 Comments   
Comment by Githook User [ 26/Jul/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36232 Fix an error in the loop which would have caused extra retry and early return
Branch: v3.6
https://github.com/mongodb/mongo/commit/c280a1829dbaf65b7fbb5bc93762776817fceae5

Comment by Githook User [ 26/Jul/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36232 Ensure chunk migration commit and the subsequent refresh are causally consistent

(cherry picked from commit 9766b4fc26fe053d6c6f92dc75500e4c1d4f5346)
Branch: v3.4
https://github.com/mongodb/mongo/commit/ca9a18a3dcea0a4bd11c690457f30f29469a85b3

Comment by Githook User [ 25/Jul/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36232 Ensure chunk migration commit and the subsequent refresh are causally consistent
Branch: v3.6
https://github.com/mongodb/mongo/commit/9766b4fc26fe053d6c6f92dc75500e4c1d4f5346

Comment by Githook User [ 23/Jul/18 ]

Author:

{'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}

Message: SERVER-36232 Ensure chunk migration commit and the subsequent refresh are causally consistent

(cherry picked from commit ba25922e6b2bffa60a8a4f3db8adca612da55e95)
Branch: v4.0
https://github.com/mongodb/mongo/commit/ef2f722627f09aba4f25ad46a557da7f416ce8da

Comment by Githook User [ 23/Jul/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36232 Ensure chunk migration commit and the subsequent refresh are causally consistent
Branch: master
https://github.com/mongodb/mongo/commit/ba25922e6b2bffa60a8a4f3db8adca612da55e95

Generated at Thu Feb 08 04:42:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.