[SERVER-47260] mongos_get_shard_version.js assumes causal consistency but isn't Created: 01/Apr/20  Updated: 29/Oct/23  Resolved: 06/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc3, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-49550 Modify mongos_get_shard_version.js to... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-04-20
Participants:
Linked BF Score: 22

 Description   

Test performs splits, moveChunk and checks the version of the mongos at the end to make sure that mongos has the version right before the moveChunk. The issue is that the splitChunk command are sent directly to the shards, this means that when mongos performs a force refresh at the beginning of moveChunk, it can get a version that is even older. And this will cause the assertion at the end to fail.



 Comments   
Comment by Githook User [ 24/Apr/20 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-47260 mongos_get_shard_version.js assumes causal consistency but isn't

(cherry picked from commit 6cd52288da7cfcfb9d7b2b5b850cb0c9e5f75024)
Branch: v4.4
https://github.com/mongodb/mongo/commit/8d6b0889e6b8b4cdcf4be81b6843d0449a31ef84

Comment by Githook User [ 06/Apr/20 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-47260 mongos_get_shard_version.js assumes causal consistency but isn't
Branch: master
https://github.com/mongodb/mongo/commit/6cd52288da7cfcfb9d7b2b5b850cb0c9e5f75024

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