[SERVER-674] Uncaught std::exception: St9bad_alloc, terminating Created: 24/Feb/10 Updated: 12/Jul/16 Resolved: 26/Feb/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 1.3.3 |
| Fix Version/s: | 1.3.3 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Bob T. Terminal | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
x86_64 |
||
| Attachments: |
|
| Participants: |
| Description |
|
Using mongodb in repl pair master randomly terminates due to St9bad_alloc, have seen 5 times now within 24hrs on multiple servers. db version v1.3.3 scons options used: --64 --prefix=$(PREFIX) --extrapath=$(PREFIX) Server setup (repl pair) db01 <----> db02 top at time of incident top - 15:49:47 up 27 days, 3:32, 4 users, load average: 0.90, 0.83, 0.62 server options used dbpath, logpath, nohttpinterface, noauth = true, pairwith = xxx |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 26/Feb/10 ] |
|
uses a new ThreadSafeString |
| Comment by auto [ 26/Feb/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: make info thread safe |
| Comment by Aaron Staple [ 25/Feb/10 ] |
|
Yeah, so I think the only problem is with the "info" string describing the context in which a master state changed. Probably we can ignore info if level == 0, otherwise we should get a lock and report info. |
| Comment by Eliot Horowitz (Inactive) [ 24/Feb/10 ] |
|
aaron: seems that maybe appendReplicationInfo might not be thread safe. |