[SERVER-58433] ReshardingCoordinatorService Transaction In bumpCollectionVersionAndChangeMetadataInTxn Possibly Too Large Created: 12/Jul/21 Updated: 29/Oct/23 Resolved: 31/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Luis Osta (Inactive) | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||||||||||
| Sprint: | Sharding 2021-08-23 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||
| Description |
|
As discovered in this ticket and discussed in this [CR|https://mongodbcr.appspot.com/799100006.] The transaction in ShardingCatalogManager that makes sure the updates in |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] | ||||
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! | ||||
| Comment by Githook User [ 05/Oct/21 ] | ||||
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: | ||||
| Comment by Githook User [ 30/Aug/21 ] | ||||
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: | ||||
| Comment by Max Hirschhorn [ 30/Jul/21 ] | ||||
|
After discussing this issue with Garaudy, I can confirm we'll need to stop using multi-statement transactions to bulk write the documents in config.chunks and config.tags as part of the different resharding coordinator state transitions. I believe we can assume that when a resharding operation is running that the config.chunks documents are keyed off of "uuid" and don't contain an "ns" field. This is because the resharding operation only runs in FCV 5.0+.
| ||||
| Comment by Max Hirschhorn [ 14/Jul/21 ] | ||||
|
In addition to the WiredTiger cache size limitations, there is also the issue of the multi-statement transaction taking longer than the 1-minute default for the transactionLifetimeLimitSeconds server parameter. I imagine this combination will leave us without any options other than to rewrite the ReshardingCoordinator to not use a multi-statement transaction for its bulk updates and deletes of config.chunks and config.tags documents. |