-
Type:
Bug
-
Resolution: Done
-
Priority:
Blocker - P1
-
Affects Version/s: 2.4.0-rc0
-
Component/s: Networking
-
None
-
Environment:OS-X
-
ALL
Problem:
With > 1024 db files, 2.4.0-rc0 (and 2.3.2) fails to start with
Mon Feb 11 21:43:47.460 [IndexRebuilder] opening db: fred98 Mon Feb 11 21:43:47.463 [IndexRebuilder] opening db: fred99 Mon Feb 11 21:43:47.465 [IndexRebuilder] opening db: local Mon Feb 11 21:43:47.468 [websvr] admin web console waiting for connections on port 28017 Mon Feb 11 21:43:47.468 [initandlisten] waiting for connections on port 27017 Mon Feb 11 21:43:47.469 [websvr] select() failure: ret=-1 errno:22 Invalid argument Mon Feb 11 21:43:47.469 [initandlisten] select() failure: ret=-1 errno:22 Invalid argument Mon Feb 11 21:43:47.469 [initandlisten] now exiting
Reproduce:
> mongod --dbpath /data/db/bug --logpath /data/db/bug/server.log --fork --smallfiles --noprealloc
Create enough DB's so that startup will be successful
> mongo admin for (i=0; i < 506; i++) { var dummyDb = db.getSisterDB( "fred" + i ).foo.insert({x:1}); } db.shutdownServer()
Startup will be ok
> mongod --dbpath /data/db/bug --logpath /data/db/bug/server.log --fork --smallfiles --noprealloc
Add another DB and shutdown
> mongo admin var dummyDb = db.getSisterDB( "fred507" ).foo.insert({x:1}); db.shutdownServer()
Startup will now fail
> mongod --dbpath /data/db/bug --logpath /data/db/bug/server.log --fork --smallfiles --noprealloc
Note:
If you take the same db files and now start them with 2.2.3 then it will startup OK.
- depends on
-
-
- Closed
-