[SERVER-35092] ShardServerCatalogCacheLoader should have a timeout waiting for read concern Created: 18/May/18  Updated: 29/Oct/23  Resolved: 21/Aug/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.9
Fix Version/s: 3.6.8, 4.0.2, 4.1.3

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-34922 mongofiles sharded cluster write conc... Closed
Problem/Incident
causes SERVER-78115 Shard primaries must commit a majorit... Closed
Related
is related to SERVER-34632 config.chunks change to config.cache.... Backlog
is related to TOOLS-2035 mongofiles_write_concern_mongos.js fa... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: Sharding 2018-08-27
Participants:
Case:
Linked BF Score: 5

 Description   

Otherwise, it can wait indefinitely.

For example:

https://github.com/mongodb/mongo/blob/r3.7.9/src/mongo/db/s/shard_server_catalog_cache_loader.cpp#L892
https://github.com/mongodb/mongo/blob/r3.7.9/src/mongo/db/s/shard_server_catalog_cache_loader.cpp#L921



 Comments   
Comment by Kaloian Manassiev [ 23/Aug/18 ]

This bug is due to the updates of the routing metadata cache unnecessarily waiting on linearizable read concern, meaning that majority of the data bearing nodes must be available. Unfortunately in the absence of quorum of data bearing nodes (such as the PSA configuration with the S being down), before 3.6.8, there is no workaround other than bringing it back up.

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}

Message: SERVER-35092 do not wait for majority dummy write when writing config metadata update

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

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}

Message: SERVER-35092 do not wait for majority dummy write when writing config metadata update

(cherry picked from commit a191c2920de18ea1f32aac6559cf6288c2cfc590)
Branch: v3.6
https://github.com/mongodb/mongo/commit/9d2e2aa0798ab510efbd10d62dba30c8fb100486

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}

Message: SERVER-35092 do not wait for majority dummy write when writing config metadata update
Branch: master
https://github.com/mongodb/mongo/commit/a191c2920de18ea1f32aac6559cf6288c2cfc590

Comment by Kaloian Manassiev [ 13/Jun/18 ]

This ticket will go away once the ShardServerCatalogCache loader is rewritten as part of SERVER-34632.

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