[SERVER-5100] writelocktry in replMasterThread may make reads hang Created: 26/Feb/12  Updated: 11/Jul/16  Resolved: 05/Jun/12

Status: Closed
Project: Core Server
Component/s: Concurrency, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.1.1

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS X 10.5 64-bit DEBUG


Issue Links:
Depends
depends on SERVER-5172 upgrade boost to 1.49 and import code... Closed
Duplicate
is duplicated by SERVER-5028 Bug in fsync2.js causes RHEL 64bit Ni... Closed
Operating System: OS X
Participants:

 Description   

http://buildbot.mongodb.org/builders/OS%20X%2010.5%2064-bit%20DEBUG/builds/733/steps/test_2/logs/stdio



 Comments   
Comment by Eliot Horowitz (Inactive) [ 02/Mar/12 ]

This is fixed by SERVER-5172

Comment by Eric Milkie [ 02/Mar/12 ]

filed SERVER-5172 to upgrade boost

Comment by Eric Milkie [ 27/Feb/12 ]

I am looking at the hung test on the Linux 32bit builder.
There are mongod's running on 27999, 30000, 30001, and 30002. 30002 is not part of the replica set and does not respond to connection requests. All the other servers have no currentOp's.

When I debugged the mongo process, all the threads were blocked waiting for output from the mongod's it had spawned, except for thread 1. Thread 1 was blocked in the js interpreter, on a JSSleep call. So presumably it's in a sleep loop in the test code.

It seems that the scenario proposed in SERVER-5028 might be the situation here.

Generated at Thu Feb 08 03:07:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.