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

Make chunk migrations metrics more accessible from Atlas

    • Sharding EMEA
    • Fully Compatible
    • v7.0, v6.3, v6.0, v5.0
    • Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
    • 4.5

      Often, when investigating HELP tickets related to balancing, we need to access and combine data from FTDC, logs and configdump to figure some basic metrics such as:

      • Migration throughput (how fast is this shard cloning data)
      • Range deleter throughout (how fast is this shard executing its range deletions)
      • Number of orphans documents (how many orphans documents are waiting to be deleted)

      The following statistics should be available on serverStatus under the shardingStatistics group (besides the currently already available):

      • countDocsClonedOnCatchUpOnRecipient: the number of documents cloned during the catch up phase of the migration
      • countBytesClonedOnCatchUpOnRecipient: the number of bytes cloned during the catch up phase of the migration
      • countDonorMoveChunkCommitted: the total number of migrations committed by the node
      • countDonorMoveChunkAborted: the number of migrations aborted in the node
      • totalDonorMoveChunkTimeMillis: the total amount of time a migration took from beginning to end
      • totalRecipientCriticalSectionTimeMillis: the amount of time in milliseconds the recipient of a migration spent holding the critical section

            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            0 Vote for this issue
            4 Start watching this issue