[SERVER-70640] Add migrationConcurrency to serverStatus Created: 17/Oct/22  Updated: 29/Oct/23  Resolved: 18/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.15, 6.3.0-rc0, 6.0.5, 6.0.6

Type: New Feature Priority: Major - P3
Reporter: Rachita Dhawan Assignee: Rachita Dhawan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-15825 [Server] Add migrationConcurrency to ... Closed
Duplicate
is duplicated by SERVER-70641 Add migrationConcurrency to serverStatus Closed
Backwards Compatibility: Minor Change
Backport Requested:
v6.0, v5.0
Sprint: Sharding 2022-10-17, Sharding NYC 2022-10-31, Sharding NYC 2022-11-14, Sharding NYC 2022-11-28, Sharding 2022-12-12, Sharding NYC 2022-12-26, Sharding NYC 2023-01-09, Sharding NYC 2023-01-23
Participants:

 Description   

We will add a new server status section to mongod:

"shardingStatistics" : {
  "countStaleConfigErrors" : NumberLong(<num>),
  "countDonorMoveChunkStarted" : NumberLong(<num>),
  "totalDonorChunkCloneTimeMillis" : NumberLong(<num>),
  "totalCriticalSectionCommitTimeMillis" : NumberLong(<num>),
  "totalCriticalSectionTimeMillis" : NumberLong(<num>),
  "countDocsClonedOnRecipient" : NumberLong(<num>),
  "countDocsClonedOnDonor" : NumberLong(<num>),
  "countRecipientMoveChunkStarted" : NumberLong(<num>),
  "countDocsDeletedOnDonor" : NumberLong(<num>),
  "countDonorMoveChunkLockTimeout" : NumberLong(<num>),
  "unfinishedMigrationFromPreviousPrimary" : NumberLong(<num>),
   * “chunkMigrationConcurrency : NumberLong(<num>),
  "catalogCache" : {....| |  },
  "rangeDeleterTasks" : <num>,
  "resharding" : {..}
}


 Comments   
Comment by Githook User [ 16/Mar/23 ]

Author:

{'name': 'Rachita Dhawan', 'email': 'rachita.dhawan@gmail.com', 'username': 'racdhawan'}

Message: SERVER-70640 Add migrationConcurrency to serverStatus

(cherry picked from commit 28a53314e42d11a11bf4dea0a40d3be164d30e8b)
Branch: v6.0
https://github.com/mongodb/mongo/commit/da29e41478885ef7bc6fe370754b5aff75a3ba27

Comment by Githook User [ 02/Mar/23 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: Revert "SERVER-70640 Add migrationConcurrency to serverStatus"

This reverts commit cc379041cd9c42ab9d2b1eed97011e3f7d6189ef.
Branch: v6.0
https://github.com/mongodb/mongo/commit/48a03d225d30b44b2ac00b7111ef8608a41c34de

Comment by Githook User [ 27/Jan/23 ]

Author:

{'name': 'Rachita Dhawan', 'email': 'rachita.dhawan@gmail.com', 'username': 'racdhawan'}

Message: SERVER-70640 Add migrationConcurrency to serverStatus

(cherry picked from commit 28a53314e42d11a11bf4dea0a40d3be164d30e8b)
(cherry picked from commit cc379041cd9c42ab9d2b1eed97011e3f7d6189ef)
Branch: v5.0
https://github.com/mongodb/mongo/commit/b6ef407dfb2b329d746dff89a5bdf650c2eac947

Comment by Githook User [ 23/Jan/23 ]

Author:

{'name': 'Rachita Dhawan', 'email': 'rachita.dhawan@gmail.com', 'username': 'racdhawan'}

Message: SERVER-70640 Add migrationConcurrency to serverStatus

(cherry picked from commit 28a53314e42d11a11bf4dea0a40d3be164d30e8b)
Branch: v6.0
https://github.com/mongodb/mongo/commit/cc379041cd9c42ab9d2b1eed97011e3f7d6189ef

Comment by Githook User [ 18/Jan/23 ]

Author:

{'name': 'Rachita Dhawan', 'email': 'rachita.dhawan@gmail.com', 'username': 'racdhawan'}

Message: SERVER-70640 Add migrationConcurrency to serverStatus
Branch: master
https://github.com/mongodb/mongo/commit/28a53314e42d11a11bf4dea0a40d3be164d30e8b

Comment by Max Hirschhorn [ 17/Oct/22 ]

My understanding from the scope document is that the goal is to have the migrationConcurrency value appear in FTDC. If my understanding is accurate then we'll want use the existing shardingStatistics server status section.

https://www.mongodb.com/docs/manual/reference/command/serverStatus/#shardingstatistics

Generated at Thu Feb 08 06:16:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.