[SERVER-48180] Make onShardVersionMismatch use ScopedShardVersionCriticalSection - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Task
Status: Closed
Priority: Major - P3
Resolution: Duplicate
Affects Version/s: None
Fix Version/s: None
Component/s: Sharding
Labels:
- PM-1645-Milestone-1

Sprint:
Sharding 2020-05-18

Description

Modify onShardVersionMismatch in order to:

Don't call directly forceShardFilteringMetadataRefresh
Wait on an ongoing shard version refresh or trigger it with a ScopedShardVersionCriticalSection object

Update forceShardFilteringMetadataRefresh:

Remove forceRefreshFromThisThread flag
Remove unused hasAdditionalCatalogCacheForFiltering part

Attachments

Issue Links

duplicates

SERVER-47975 Optimize ScopedShardVersionCriticalSection in order to avoid convoy on SSV after a shardVersion change

Closed

Activity

People

Assignee:: Pierlauro Sciarelli

Reporter:: Pierlauro Sciarelli

Participants:: Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: May 13 2020 10:43:53 AM UTC

Updated:: May 13 2020 11:04:31 AM UTC

Resolved:: May 13 2020 11:04:23 AM UTC