[SERVER-55385] Remove dedicated thread pools for each ReshardingOplogApplier Created: 20/Mar/21  Updated: 29/Oct/23  Resolved: 09/Apr/21

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

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

Issue Links:
Depends
depends on SERVER-55384 Move session application for reshardi... Closed
Duplicate
is duplicated by SERVER-53139 Don't wait for prepared transactions ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-04-19
Participants:
Story Points: 2

 Description   

Each ReshardingOplogApplier instance (one per donor shard) currently receives its own ThreadPool for actually performing oplog application. Sizing the number of threads to use for resharding would be simpler for end users if there was only one of them, i.e. RecipientStateMachine's task executor.



 Comments   
Comment by Githook User [ 09/Apr/21 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-55385 Use common executor to apply oplog entries in resharding.

Removes the dedicated thread pools for each ReshardingOplogApplier to
apply oplog entries with.

Renames the reshardingWriterThreadCount server parameter to be called
reshardingOplogBatchTaskCount.

Adds a ReshardingOplogBatchApplier class to apply batches of oplog
entries without blocking the thread on prepared transactions during
session application.
Branch: master
https://github.com/mongodb/mongo/commit/cd5acd79d124fdb2552c411963eb7c29019ffc26

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