[SERVER-2822] secondary cannot recover after failure Created: 23/Mar/11 Updated: 12/Jul/16 Resolved: 24/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | ofer samocha | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
v.1.8.0 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
two of our 80 mongo servers has been hanged for a while, then machine was restarted. please help Wed Mar 23 01:10:39 [initandlisten] Assertion: 10334:Invalid BSONObj size: 1845624949 (0x7500026E) first element: : ?type=115 |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 24/Mar/11 ] |
|
There is no known issue with exhausting memory. |
| Comment by ofer samocha [ 24/Mar/11 ] |
|
we have zabbix, but it only show loadavg increasing till the agent stopped responsing I'll check and try munin for the next time. anyway if there is a known issue on memory exhausting, I think that was the problem. |
| Comment by Eliot Horowitz (Inactive) [ 24/Mar/11 ] |
|
Hard to tell without any monitoring or logs. |
| Comment by ofer samocha [ 24/Mar/11 ] |
|
it worked ok. Any known issue for the mongod problem that killed the machines. |
| Comment by ofer samocha [ 24/Mar/11 ] |
|
will do. thanks |
| Comment by Eliot Horowitz (Inactive) [ 24/Mar/11 ] |
|
Running with --journal or not is up to you. Yes, for resync, you just need to wipe data. |
| Comment by ofer samocha [ 24/Mar/11 ] |
|
the mongo process killed the machine until it restarted itself (and killed the mongod process) |
| Comment by Eliot Horowitz (Inactive) [ 24/Mar/11 ] |
|
You did a hard reboot? |
| Comment by ofer samocha [ 23/Mar/11 ] |
|
This bug is in core server |