[SERVER-8251] Startup hangs infinitely, DataFileSync background job cannot create new thread Created: 20/Jan/13 Updated: 15/Feb/13 Resolved: 22/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | WangYu | Assignee: | Andy Schwerin |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS release 5.8 (Final), 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:43 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux |
||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Installed the 2.2.0 rpm package from 10gen repo. 'service mongod start' creates 3 processes: root 12603 9583 0 12:59 pts/0 00:00:00 /bin/sh /sbin/service mongod restart strace of PID 12648, the third - obviously hanging - process gives: ) = -1 ETIMEDOUT (Connection timed out) ) = -1 ETIMEDOUT (Connection timed out) ) = -1 ETIMEDOUT (Connection timed out) gdb: Thread 2 (Thread 0x40a87940 (LWP 12649)): Thread 1 (Thread 0x2b5613d478c0 (LWP 12648)): This behaviour is somewhat random, because sometimes the startup works. Notes: I rebuilt mongod from source r2.2.0, stripped the binary manually and to my surprise this binary, does not show this behaviour. Alas, another binary installed with 'scons install' always hangs. |
| Comments |
| Comment by Andy Schwerin [ 22/Jan/13 ] |
|
Reproduced and confirmed duplicate of |
| Comment by Andy Schwerin [ 22/Jan/13 ] |
|
Two more questions. 1.) What is your virtualization platform – Amazon EC2, VMWare, Qemu/KVM, or something else? 2.) Do you see this hang with the 2.2.2 release (the current version) or just 2.2.0? I believe this problem will affect both problems, but continue to have trouble constructing a repro in house. |
| Comment by WangYu [ 22/Jan/13 ] |
|
It's a VM. This issue usually happened when the CPU utilization is high. |
| Comment by Andy Schwerin [ 20/Jan/13 ] |
|
I've heard of users experiencing this before, but have yet to reproduce it. Can you describe your hardware or virtual machine configuration? |