[SERVER-1862] server does not start in time in pair7.js test Created: 27/Sep/10 Updated: 19/May/14 Resolved: 14/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
<http://buildbot.mongodb.org/builders/Linux%2064-bit/builds/2017/steps/test_3/logs/stdio> m31002| Mon Sep 27 01:35:21 MongoDB starting : pid=11078 port=31002 dbpath=/data/db/jstests_pair7test-right 64-bit catch (e) { catch (e) {\n }\n return false;\n}, msg:unable to connect to mongo program on port 31002")@shell/utils.js:31 catch (e) {}return false;}),"unable to connect to mongo program on port 31002",60000)@shell/utils.js:117 Mon Sep 27 01:36:22 uncaught exception: assert.soon failed: function () { catch (e) { |
| Comments |
| Comment by Aaron Staple [ 14/Jun/11 ] |
|
we phased out replica pairs |
| Comment by Eliot Horowitz (Inactive) [ 16/Jan/11 ] |
|
pairs are deprecated, so probably not worth looking at |
| Comment by Aaron Staple [ 27/Sep/10 ] |
|
more log from above: m31002| Mon Sep 27 01:36:22 got kill or ctrl c or hup signal 15 (Terminated), will terminate after current cmd ends The shell was unable to connect to the spawned mongod instance. Since the log message "waiting for connections..." was not printed, the db apparently had not completed its initialization after 60 seconds. From looking at passing runs of pair7 on the same machine, it appears that certain mongod instances take 10 seconds to initialize. I logged on to the machine to run some tests, and it appears that the delay is occurring when we fsync a new lock file, in particular when we have just cleared that lock file's dbpath. There's a big difference between 10 sec and 60 sec, but potentially the fsync issue is related to the pair7 test failure. |