[SERVER-11670] attempt to create a large collection in local db causes continuous asserts Created: 12/Nov/13 Updated: 11/Jul/16 Resolved: 13/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Run large aggregation (of oplog.rs for example) with "out" parameter.
|
||||||||
| Participants: | |||||||||
| Description |
|
I was running aggregations and writing output to a file, but my database I was analyzing was "local" DB. Apparently if _aCommitIsNeeded detects that we have a write lock on "local" DB it fasserts() but since I'm running a regular build, it just continues fasserting till I kill -9 it. |
| Comments |
| Comment by Githook User [ 13/Feb/14 ] | ||||||||||||||||||||||||||
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: | ||||||||||||||||||||||||||
| Comment by Asya Kamsky [ 25/Jan/14 ] | ||||||||||||||||||||||||||
|
edward.norris@lumension.com regardless of this ticket, it is not ok to write anything to local database - it is for MongoDB's use and using it for user collections (to avoid replicating them) is not guaranteed to not cause problems (other than this problem you already ran into). | ||||||||||||||||||||||||||
| Comment by Ed Norris [ 23/Jan/14 ] | ||||||||||||||||||||||||||
|
I'm seeing something similar with 2.4.9 on Windows. (The reason I'm writing to the local DB is that I'm doing a mapreduce operation on a replication set and I figure it will save a little time if the raw pre-reduced data doesn't get replicated. The output of the mapreduce operation goes to a replicated DB. If this is a bad idea, let me know) | ||||||||||||||||||||||||||
| Comment by Asya Kamsky [ 07/Dec/13 ] | ||||||||||||||||||||||||||
|
I had about 4700 of these in my log:
Which seems to be caused by this:
So, dassert which I thought I tracked down to
but I see that's only on _DEBUG builds. So, I guess it's not an assert, just an infinite loop of stack traces... | ||||||||||||||||||||||||||
| Comment by Andy Schwerin [ 06/Dec/13 ] | ||||||||||||||||||||||||||
|
asya, you mean that it masserts, right? fasserts are fatal. |