[SERVER-26531] jumbo flag in chunk can be cleared when the shard that owns it donates a chunk Created: 07/Oct/16  Updated: 23/Sep/19  Resolved: 27/Jun/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.0-rc0, 3.4.21, 3.6.13, 4.0.10
Fix Version/s: 3.6.14, 4.0.11, 4.2.0-rc3, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Kaloian Manassiev
Resolution: Done Votes: 1
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-26688 Chunks consisting of a single shard k... Closed
is duplicated by SERVER-27356 Chunk is not marked as jumbo when it ... Closed
Related
related to SERVER-43524 Complete TODO listed in SERVER-26531 Closed
is related to SERVER-26527 scale down jumbo1.js Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2, v4.0, v3.6
Sprint: Sharding 2019-07-01
Participants:
Case:

 Description   

During the commit phase of the migration, the moveChunk command will set the chunk being migrated with a new major version and selects a random chunk of the current shard to have the same major version. This is done using replacement update so if a chunk that gets selected is a jumbo chunk, the flag will get cleared inadvertently.

Also uncomment this line in test after fixing:
https://github.com/mongodb/mongo/blob/27b771a1805871c1a87fab70d38e44b072b22c7f/jstests/sharding/jumbo1.js#L51



 Comments   
Comment by Githook User [ 30/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-26531 Change ConfigServerTestFixture::setupChunks to `void`

... because having it return Status just so all callers can assert that
it's OK is useless.

(cherry picked from commit 4b955e6a1a35b1704a05aa29bd7e6ed42612333c)
Branch: v3.6
https://github.com/mongodb/mongo/commit/0ae4abfd8774ea10675ebe6e114b2d3a9a7ebfdd

Comment by Githook User [ 30/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-26531 Don't reset the control chunk's 'jumbo' flag on migration commit

(cherry picked from commit 8fd79fe845e3e4717df26abb78c3fb7859f3823e)
Branch: v3.6
https://github.com/mongodb/mongo/commit/f37383b66613831046041e1c0fdfa7ed2fbc2da0

Comment by Githook User [ 30/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-26531 Change ConfigServerTestFixture::setupChunks to `void`

... because having it return Status just so all callers can assert that
it's OK is useless.

(cherry picked from commit 4b955e6a1a35b1704a05aa29bd7e6ed42612333c)
Branch: v4.0
https://github.com/mongodb/mongo/commit/ce5e56f2c2c82b0ec65c8c8957326fe96bf1a7e7

Comment by Githook User [ 30/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-26531 Don't reset the control chunk's 'jumbo' flag on migration commit

(cherry picked from commit 8fd79fe845e3e4717df26abb78c3fb7859f3823e)
Branch: v4.0
https://github.com/mongodb/mongo/commit/861013e35652e73fab0b97f534b73fce68a8e00e

Comment by Githook User [ 30/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-26531 Change ConfigServerTestFixture::setupChunks to `void`

... because having it return Status just so all callers can assert that
it's OK is useless.

(cherry picked from commit 4b955e6a1a35b1704a05aa29bd7e6ed42612333c)
Branch: v4.2
https://github.com/mongodb/mongo/commit/0ca646b3dec149d6ccdb33bbc8c7d962129bdd82

Comment by Githook User [ 30/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-26531 Don't reset the control chunk's 'jumbo' flag on migration commit

(cherry picked from commit 8fd79fe845e3e4717df26abb78c3fb7859f3823e)
Branch: v4.2
https://github.com/mongodb/mongo/commit/8b26f9dce880daf66cc98c716c819095c4d5027f

Comment by Githook User [ 27/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}

Message: SERVER-26531 Change ConfigServerTestFixture::setupChunks to `void`

... because having it return Status just so all callers can assert that
it's OK is useless.
Branch: master
https://github.com/mongodb/mongo/commit/4b955e6a1a35b1704a05aa29bd7e6ed42612333c

Comment by Githook User [ 27/Jun/19 ]

Author:

{'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}

Message: SERVER-26531 Don't reset the control chunk's 'jumbo' flag on migration commit
Branch: master
https://github.com/mongodb/mongo/commit/8fd79fe845e3e4717df26abb78c3fb7859f3823e

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