Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.17, 3.6.7, 4.0.2, 4.1.1
Affects Version/s: None
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.0, v3.6, v3.4
Sprint:
Sharding 2017-12-04, Sharding 2018-07-02, Sharding 2018-07-16, Sharding 2018-07-30
Case:
Linked BF Score:
0
Confidence Status:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

We currently upsert one document at a time in the receive portion of chunk migration. We should be able to batch insert documents and fall back to one-at-a-time if there is an error. This should be a performance win, but needs to be tested.

depends on

SERVER-35849 Remove dependency of the write commands on `sharding_runtime_d`

Closed

is duplicated by

SERVER-22196 Sharding migrateClone phase should use insert and not upsert

Closed

is related to

SERVER-8835 _secondaryThrottle should GLE after every N documents rather than after each

Closed

related to

SERVER-32885 Overlap chunk clone application on the donor with fetching documents from the recipient

Closed

SERVER-37080 Implement tuneable batch size for chunk migrations

Closed

Assignee:: Cheahuychou Mao

Reporter:: Daniel Pasette (Inactive)

Participants:: Cheahuychou Mao, Daniel Pasette, Githook User

Votes:: 0 Vote for this issue

Watchers:: 16 Start watching this issue

Created:: Jan 17 2017 11:01:16 PM UTC

Updated:: Nov 23 2022 10:53:27 PM UTC

Resolved:: Jul 20 2018 06:21:42 PM UTC

Confidence Status Last Update:: 19/Jul/18 5:52 PM

GA Target Date:: None

Public Preview Target Date:: None

Private Preview Target Date:: None

Experiment Target Date:: None

Details

Description

Attachments

Issue Links

Activity

People

Dates