[SERVER-4711] Don't use masserts when getChunkManager() fails to find a current chunk manager. Created: 18/Jan/12 Updated: 11/Jul/16 Resolved: 22/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by auto [ 22/Feb/12 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Core issue is that printing stack traces here is not entirely safe, also slow. |