[SERVER-40346] Write shardCollection initial chunks with BatchWriter Created: 26/Mar/19 Updated: 29/Oct/23 Resolved: 16/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.0.7, 4.1.9 |
| Fix Version/s: | 4.1.10, 4.0.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Sharding 2019-04-08, Sharding 2019-04-22 | ||||||||
| Participants: | |||||||||
| Description |
Problem StatementCurrently, when we shard a collection, we write each chunk document to the config server sequentially, using a {w:majority} write. This means that for 10,000 chunks we will make 10,000 calls from a shard to the config server. We can prevent this by batch writing these documents instead. Proposed Solution
|
| Comments |
| Comment by Githook User [ 04/Jun/19 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit 29ef1a415c74c883746325f13a8eaaa1831f8102) |
| Comment by Githook User [ 16/Apr/19 ] |
|
Author: {'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}Message: |
| Comment by Kaloian Manassiev [ 03/Apr/19 ] |
|
This approach LGTM. For the AlternativeSessionRegion class, in order to avoid people finding new "clever" usages of it, can you please keep it contained to the file where insertConfigDocumentsAsRetryableWrite will be implement? |
| Comment by Blake Oler [ 01/Apr/19 ] |
|
kaloian.manassiev can I get an LGTM on the approach? |