Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.1.6
Component/s: Sharding
Labels:
- 32qa

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 9 (09/18/15), Sharding A (10/09/15)
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

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

There have been at least 3 crashes in sharding code caused by use-after-frees or the misuse of references in the 3.1.x cycle: ~~SERVER-19367~~, ~~SERVER-19839~~, and ~~SERVER-18815~~ (the last commit)

We should proactively search for similar issues to avoid costly debugging later.

is related to

SERVER-19367 Segfault establishing shard connection in Chunk::splitMulti

Closed

SERVER-19839 Use-after-free in ShardRegistry::runCommandWithNotMasterRetries

Closed

SERVER-18815 Shard object lifetime shoud be managed by the ShardRegistry

Closed

related to

SERVER-20559 Race condition in shard registry during concurrent sharding operations

Closed

SERVER-20629 Use-after-free in CatalogManagerReplicaSet::_runReadCommand

Closed

Assignee:: Andy Schwerin

Reporter:: Kamran K. (Inactive)

Participants:: Andy Schwerin, Kamran K.

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: Aug 13 2015 04:05:38 PM UTC

Updated:: Sep 25 2015 07:26:48 PM UTC

Resolved:: Sep 25 2015 07:26:48 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates