Move force primary refresh functionality out of the ShardServerCatalogCacheLoader into the ShardingState's refresh logic

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA
    • Sharding 2017-12-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We want to simplify the ShardServerCatalogCacheLoader by making a simple local loader and reader of chunk metadata. So we want to move the remote call to ensure the primary has refreshed to the latest metadata out of the ShardServerCatalogCacheLoader and instead place this functionality at a higher level in the refresh logic in ShardingState::onStaleShardVersion. A rough sketch:

      onStaleShardVersion(wantedVersion) {
    while () {
        invalidateCatalogCacheMetadata
        refreshAndLoadLocalChunkMetadata
        if (wantedVersion > locallyRefreshedVersion) {
            optime = forcePrimaryRefresh
            waitForOptime(optime)
        }
    }
}

            Assignee:
            [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: