Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: 4.5.1
Component/s: Sharding
Labels:
- PM-1645-Milestone-1
- sharding-csrs-stepdown-only

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10
Linked BF Score:
40
Confidence Status:
None
Work Order:
3

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

Right now, if _configsvrCommitChunkMigration is run twice upon the config server, the second call results in an error even if the migration actually succeeded.

Possible fixes:

On the config server, checking both donor and recipient in checkChunkMatchesRequest
On the shard, double check that the chunk is still owned before a call to _configsvrCommitChunkMigration (it doesn't make the command idempotent, but it guarantees that it doesn't get called more than once)

causes

SERVER-50215 _configsvrCommitChunkMigration might return before changes are majority committed

Closed

SERVER-50458 Re-enable retryability of commitChunkMigration on the config server

Closed

SERVER-50577 Return actual donor shard version in getShardAndCollectionVersion

Closed

Assignee:: Pierlauro Sciarelli
Reporter:: Pierlauro Sciarelli
Participants:: Githook User, Pierlauro Sciarelli
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jun 26 2020 05:12:23 PM UTC
Updated:: Oct 29 2023 10:06:23 PM UTC
Resolved:: Jul 29 2020 10:26:41 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates