[SERVER-68928] Store placement changes into config.placementHistory when a moveChunk/Range() command gets committed on the config server Created: 18/Aug/22  Updated: 29/Oct/23  Resolved: 10/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14
Participants:

 Description   

The completion of a chunk migration may a change to the placement metadata of the collection it belongs to:

  • the donor gives away the last chunk of nss it was owning
  • the recipient takes ownership of its first chunk of nss

Such events must be matched with related writes to config.placementHistory.



 Comments   
Comment by Githook User [ 10/Nov/22 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-68928 Persist historical placement metadata when moveChunk() is committed
Branch: master
https://github.com/mongodb/mongo/commit/492a1bc089229e25595aee837ee2f38e4c00eba6

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