[SERVER-2076] killall may fail in v8 Created: 08/Nov/10  Updated: 12/Jul/16  Resolved: 07/Oct/11

Status: Closed
Project: Core Server
Component/s: JavaScript
Affects Version/s: None
Fix Version/s: 2.1.0

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Antoine Girbal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-1900 v8 Issue 708 Closed
is depended on by SERVER-387 currentOp() and killOp() don't work r... Closed
is depended on by SERVER-2407 Switch to v8 Closed
Operating System: ALL
Participants:

 Description   

In the killall.js test, we timed out before all ops were killed.

I'm adding some comments to the test to make the expected behavior more clear.



 Comments   
Comment by Antoine Girbal [ 07/Oct/11 ]

reenabled test, this passes now, see SERVER-1900

Comment by auto [ 07/Oct/11 ]

Author:

{u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}

Message: - SERVER-2076: killall may fail in v8
Branch: master
https://github.com/mongodb/mongo/commit/d312c1abe458919c977cbb82ba3970f8af456478

Comment by Antoine Girbal [ 22/Aug/11 ]

can't seem to have this test fail with v8.
Have been running it in a loop and after 500 times no sign of failure.

Comment by auto [ 01/Feb/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-2076 disable test in v8 mode
https://github.com/mongodb/mongo/commit/841a56ba4caf9cfff8c456cf183c78d7c2a61ab5

Comment by Aaron Staple [ 01/Feb/11 ]

These failures may result from SERVER-1900, though I haven't confirmed with certainty that they do.

Comment by Aaron Staple [ 01/Feb/11 ]

I think we've only seen this failure in v8 mode.

Comment by auto [ 08/Nov/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-2076 comment
/mongodb/mongo/commit/d0456e59b289a56c18f324ad6740cd2ce1f71ddf

Comment by Aaron Staple [ 08/Nov/10 ]

connecting to: 127.0.0.1:32000/test
WARNING DELETES DATA DIRECTORY THIS IS FOR TESTING RENAME YOUR INVOCATION
shell: started program /home/yellow/buildbot/Linux_64bit_v8/mongo/mongod --port 31000 --dbpath /data/db/jstests_disk_killall
m31000| Mon Nov 8 09:38:13 MongoDB starting : pid=28571 port=31000 dbpath=/data/db/jstests_disk_killall 64-bit
m31000|
m31000| ** NOTE: This is a development version (1.7.3-pre-) of MongoDB.
m31000| ** Not recommended for production.
m31000|
m31000| Mon Nov 8 09:38:13 db version v1.7.3-pre-, pdfile version 4.5
m31000| Mon Nov 8 09:38:13 git version: 2d3e8a8b73f55f74efaf0d0a49cd4b6a9fc1d815
m31000| Mon Nov 8 09:38:13 sys info: Linux sb1.10gen.cc 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:18:33 EDT 2007 x86_64 BOOST_LIB_VERSION=1_41
m31000| Mon Nov 8 09:38:13 [initandlisten] waiting for connections on port 31000
m31000| Mon Nov 8 09:38:13 [websvr] web admin interface listening on port 32000
m31000| Mon Nov 8 09:38:13 [websvr] listen(): bind() failed errno:98 Address already in use for socket: 0.0.0.0:32000
m31000| Mon Nov 8 09:38:13 [websvr] addr already in use
m31000| Mon Nov 8 09:38:13 [initandlisten] connection accepted from 127.0.0.1:50522 #1
m31000| Mon Nov 8 09:38:13 allocating new datafile /data/db/jstests_disk_killall/test.ns, filling with zeroes...
m31000| Mon Nov 8 09:38:13 done allocating datafile /data/db/jstests_disk_killall/test.ns, size: 16MB, took 0.026 secs
m31000| Mon Nov 8 09:38:13 allocating new datafile /data/db/jstests_disk_killall/test.0, filling with zeroes...
m31000| Mon Nov 8 09:38:13 done allocating datafile /data/db/jstests_disk_killall/test.0, size: 64MB, took 0.105 secs
m31000| Mon Nov 8 09:38:13 [conn1] building new index on

{ _id: 1 }

for test.jstests_disk_killall
m31000| Mon Nov 8 09:38:13 [conn1] done for 0 records 0secs
m31000| Mon Nov 8 09:38:13 [conn1] insert test.jstests_disk_killall 137ms
m31000| Mon Nov 8 09:38:13 allocating new datafile /data/db/jstests_disk_killall/test.1, filling with zeroes...
shell: started program /home/yellow/buildbot/Linux_64bit_v8/mongo/mongo --port 31000 --eval db.jstests_disk_killall.count( { $where: function() { while( 1 )

{ ; }

} } )
sh28582| MongoDB shell version: 1.7.3-pre-
m31000| Mon Nov 8 09:38:13 [initandlisten] connection accepted from 127.0.0.1:50523 #2
m31000| Mon Nov 8 09:38:14 done allocating datafile /data/db/jstests_disk_killall/test.1, size: 128MB, took 0.626 secs
shell: started program /home/yellow/buildbot/Linux_64bit_v8/mongo/mongo --port 31000 --eval db.jstests_disk_killall.drop()
sh28587| MongoDB shell version: 1.7.3-pre-
m31000| Mon Nov 8 09:38:14 [initandlisten] connection accepted from 127.0.0.1:50524 #3
m31000| Mon Nov 8 09:38:15 got kill or ctrl c or hup signal 15 (Terminated), will terminate after current cmd ends
Mon Nov 8 09:38:45 process on port 31000, with pid 28571 not terminated, sending sigkill
sh28582| fork() available!
sh28582| connecting to: 127.0.0.1:31000/test
sh28582| Mon Nov 8 09:38:45 exec error: shell/query.js:159 count failed: null
sh28582| throw "count failed: " + tojson( res );
sh28582| ^
sh28582|
sh28587| fork() available!
sh28587| connecting to: 127.0.0.1:31000/test
sh28587| Mon Nov 8 09:38:45 exec error: shell/collection.js:326 TypeError: Cannot read property 'ok' of null
sh28587| if ( ! ret.ok ){
sh28587| ^
sh28587|
shell: stopped mongo program on port 31000
assert: [12] != [0] are not equal : undefined
Error: Printing Stack Trace (lines are 0-based in spidermonkey)
at shell/utils.js:21:7
at shell/utils.js:32:1
at Function.eq (shell/utils.js:60:42)
at /home/yellow/buildbot/Linux_64bit_v8/mongo/jstests/disk/killall.js:19:8
Mon Nov 8 09:38:50 exec error: shell/utils.js:33 [12] != [0] are not equal : undefined
throw msg;
^

failed to load: /home/yellow/buildbot/Linux_64bit_v8/mongo/jstests/disk/killall.js

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