Refactor catalog client classes to accommodate shards reading/writing to shard collections

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-02-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ShardingCatalogManager handles metadata operations on the config server. Commands come to the config server, and a method on the catalogManager is usually called (or should be).

      ShardingCatalogClient handles reading config server metadata, though it also currently manipulates config metadata because commands haven't been moved from the mongos to config server yet. The intention, however, is for it to be a reader.

      Since shard chunk metadata will be written to shard config.chunks.uuid collections, we have a new category of operations. This ticket is to come up with a class structure proposal, then rename existing and create new classes, and implement methods to read and write to config.chunks.uuid. The new methods will roughly be:

      std::vector<ChunkType> readShardChunks(OperationContext* txn, const NamespaceString& nss);
Status writeShardChunks(OperationContext* txn, std::vector<ChunkType> chunks);

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: