Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:
None

Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

Currently there's a map in s/shard_version.cpp that associated each client connection with a shard version. Might be better to store that version in each thread's thread-local ClientBase object.

related to

SERVER-7460 Issue with threads re-using previously released memory containing a Shard version

Closed

SERVER-1714 multiplex mongos -> mongod connecions after successful read op

Closed

Assignee:: Unassigned
Reporter:: Spencer Brody (Inactive)
Participants:: Greg Studer, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Nov 09 2012 08:18:15 PM UTC
Updated:: Mar 07 2014 05:15:13 PM UTC
Resolved:: Mar 07 2014 05:15:13 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates