Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50910

Make ShardRegistry::_getData() async

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0-alpha0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible

      This will eliminate the cumbersome need to use a thread just to schedule a ShardRegistry lookup (when incorporating RSM changes).

      ie. instead of returning _cache->acquire(...), _getData() can return _cache->acquireAsync(...), and no longer need to take an opCtx (the VectorClock can be obtained via _service instead). Most callers will then just call .get(opCtx) on the result from _getData(). But callers such as the above, which are just scheduling a lookup and aren't interested in the result, don't need to do that.

            Assignee:
            jaume.moragues@mongodb.com Jaume Moragues (Inactive)
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: