Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.1.1
Affects Version/s: None
Component/s: Sharding
Labels:
None

Operating System:
ALL

Printing the stack trace takes a long time, and this really isn't a very exceptional condition. Also, running printStackTrace() isn't particularly stable - see http://buildbot.mongodb.org/builders/Linux%2064-bit/builds/4064/steps/test_3/logs/stdio/text.

is depended on by

SERVER-4220 refactor getChunkManager() and sharding code to better handle parallel queries.

Closed

is duplicated by

SERVER-4956 mongos sharding assertion in shard3.js unit test from RHEL build

Closed

SERVER-5029 shard3.js test failure and hang

Closed

is related to

SERVER-4732 potential segfault on full config reload during wbl if collection is dropped / unsharded but still receives writebacks

Closed

Assignee:: Greg Studer

Reporter:: Greg Studer

Participants:: auto, Greg Studer

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: Jan 18 2012 03:56:57 PM UTC

Updated:: Jul 11 2016 06:34:55 PM UTC

Resolved:: Feb 22 2012 04:52:05 PM UTC