[SERVER-42395] Add diagnosability and supportability features for refining a shard key Created: 24/Jul/19  Updated: 29/Oct/23  Resolved: 05/Aug/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: James Heppenstall (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-08-12
Participants:

 Description   

As described in the diagnosis/debuggability section of the design document, the following behavior should be added:

  1. Log to the config server primary’s main log timing stats at each phase of the transaction used to refine a collection’s shard key.
    • e.g. before and after updating the collection document, after updating each chunk, and after updating each zone range.
  2. Add change log writes at beginning and end of refining a shard key.


 Comments   
Comment by Githook User [ 05/Aug/19 ]

Author:

{'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'username': 'JamesHeppenstall'}

Message: SERVER-42395 Add diagnosability and supportability features for refineCollectionShardKey
Branch: master
https://github.com/mongodb/mongo/commit/76208a78621cfe67d417a5781f9202580f1b2608

Generated at Thu Feb 08 05:00:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.