Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13786

Investigate changes in SERVER-49307: In changelog, report the shard name (& server host:port) for the shard that owns the chunk, instead of CSRS replica set name (& CSRS primary host:port)

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      3
    • Sprint:
      ServerDocs2021: Aug17 - Aug24

      Description

      Description

      Downstream Change Summary

      Changelog entries for split and merge now have a new field called "owningShard" under the "details" section of the entry. This refers to the shardId of the shard that owns the chunk(s) that were split or merged.

      A changelog entry for a chunk split will now look something like:

      {
        "_id" : "CSRS_primary_host:CSRS_primary_port-XXX-YYY",
        "server" : "CSRS_primary_host:CSRS_primary_port",
        "shard" : "config",
        "time" : ISODate("2020-23-07T00:00:00.00"),
        "what" : "split",
        "ns" : "db.collection",
        "details" : {
          "before" : {
             ...
          },
          "left" : {
             ...
          },
          "right" : {
             ...
          },
          "owningShard": shardId
       }
      }
      

      Description of Linked Ticket

      After a chunk is split, a split event will be recorded in the config.changelog collection. Currently the shard name & server name recorded in this changelog is the replica set of CSRS and host:port of the CSRS primary.

      	"_id" : "CSRS_primary_host:CSRS_primary_port-XXX-YYY",
      	"server" : "CSRS_primary_host:CSRS_primary_port",
      	"shard" : "config",
      

      It would be nice if the shard name & server could be the shard that owns the chunk. This would help to check the split activities on the shards and might help to identify hot shards etc.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jeffrey.allen Jeffrey Allen
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Jeffrey Allen Jeffrey Allen
              Docs Reviewer:
              Jason Price Jason Price
              External Reviewer:
              Janna Golden
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                9 weeks, 4 days ago
                Date of 1st Reply: