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

Shard object lifetime shoud be managed by the ShardRegistry

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.5
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Minor Change
    • Sharding 4 06/05/15, Sharding 5 06/26/16

      The Shard object should become the container for all shard connections, targeting and monitoring logic.

      Thus, it should be made non-copyable and it's lifetime should be managed by the ShardRegistry.

      A new type ShardId should be introduced, which will be used in all places which store Shard values currently.

            Assignee:
            daniel.alabi@10gen.com Daniel Alabi
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: