Hi Evan, It is deinitely the case. And it still does not work... I have tried to update CB and ran into this issue. It makes CB+mongo practically useless
Peter On Thursday, January 17, 2013 6:57:57 PM UTC+1, Evan Miller wrote: > > On Sun, Dec 16, 2012 at 12:01 PM, Eugen Vitzer <[email protected]<javascript:> > > wrote: > >> Those are really small things... I am aware of the possibility that I >> could import the data using MongoDB scripts. But I wonder if it could do it >> within CB, issuing a large number of "BossRecord:save()" within one single >> request (processing input file lines one per one). It seems that I'm >> hitting a limit of some kind, but cannot figure it out. > > > Hmm... I wonder if the Mongo adapter is not properly closing ports on the > Erlang side. Can you try a lsof -i when you're hitting the error condition > and see if there are a bunch (~ thousands) of open ports? > > Evan > > >> >> Eugen >> >> >> On Sunday, December 16, 2012 6:50:08 PM UTC+1, Kai Janson wrote: >> >>> Just recently I imported 1.17 million rows (=documents) into MongoDB and >>> some of them were really large. I did not encounter any problems either >>> querying or updating. The super large ones "take a moment" to update, but >>> eventually they will go thru. >>> >>> Makes me wonder how large your things are that you're trying to get in >>> and out of mongodb. >>> >>> --Kai >>> >>> Sent from my tricorder >>> >>> On Dec 16, 2012, at 11:27 AM, "Lindorfer, Eugen" <[email protected]> >>> wrote: >>> >>> I have been using Chicagoboss with the MongoDB adapter for developing a >>> proof-of-concept (currently on Mac OSX) for a website. Basically, almost >>> everything runs fine - performance is extraordinary good. >>> But I have a problem with certain requests that are used to read large >>> datasets from file. After a few thousand lines are imported without >>> problem, this error appears: >>> >>> =CRASH REPORT==== 16-Dec-2012::11:43:11 === >>> crasher: >>> initial call: supervisor:poolboy_sup/1 >>> pid: <0.16738.1> >>> registered_name: [] >>> exception exit: {{badmatch, >>> {error, >>> {{badmatch,{error,eaddrnotavail}}, >>> [{boss_db_adapter_mongodb,init,1, >>> [{file, >>> "src/db_adapters/boss_db_ >>> adapter_mongodb.erl"}, >>> {line,29}]}, >>> {boss_db_controller,init,1, >>> [{file,"src/boss_db_ >>> controller.erl"},{line,31}]}, >>> {gen_server,init_it,6, >>> [{file,"gen_server.erl"},{line,304}]}, >>> {proc_lib,init_p_do_apply,3, >>> [{file,"proc_lib.erl"},{line,227}]}]}}}, >>> [{poolboy,new_worker,2, >>> [{file,"src/poolboy.erl"},{line,348}]}, >>> {poolboy,prepopulate,4, >>> [{file,"src/poolboy.erl"},{line,370}]}, >>> {poolboy,init,2,[{file,"src/ >>> poolboy.erl"},{line,74}]}, >>> {gen_fsm,init_it,6,[{file," >>> gen_fsm.erl"},{line,361}]}, >>> {proc_lib,init_p_do_apply,3, >>> [{file,"proc_lib.erl"},{line,227}]}]} >>> in function gen_server:terminate/6 (gen_server.erl, line 747) >>> ancestors: [boss_db_pool,boss_db_sup,boss_web,boss_sup,<0.57.0>] >>> messages: [] >>> links: [] >>> dictionary: [] >>> trap_exit: true >>> status: running >>> heap_size: 1597 >>> stack_size: 24 >>> reductions: 468 >>> neighbours: >>> >>> Definitly, the error has nothing to do with the structure of the data. >>> In MongoDB log we see that we (sort of) "run out" of local ports: >>> >>> Sun Dec 16 11:43:11 [conn16366] end connection 127.0.0.1:60240 (4 >>> connections now open) >>> Sun Dec 16 11:43:11 [initandlisten] connection accepted from >>> 127.0.0.1:60245 #16370 (5 connections now open) >>> Sun Dec 16 11:43:11 [conn16367] end connection 127.0.0.1:60242 (4 >>> connections now open) >>> Sun Dec 16 11:43:11 [initandlisten] connection accepted from >>> 127.0.0.1:60246 #16371 (5 connections now open) >>> Sun Dec 16 11:43:11 [conn16368] end connection 127.0.0.1:60243 (4 >>> connections now open) >>> Sun Dec 16 11:43:11 [initandlisten] connection accepted from >>> 127.0.0.1:60247 #16372 (5 connections now open) >>> Sun Dec 16 11:43:11 [conn16369] end connection 127.0.0.1:60244 (4 >>> connections now open) >>> Sun Dec 16 11:43:11 [initandlisten] connection accepted from >>> 127.0.0.1:60248 #16373 (5 connections now open) >>> Sun Dec 16 11:43:11 [conn16370] end connection 127.0.0.1:60245 (4 >>> connections now open) >>> Sun Dec 16 11:43:11 [initandlisten] connection accepted from >>> 127.0.0.1:60256 #16374 (5 connections now open) >>> Sun Dec 16 11:43:11 [conn16371] end connection 127.0.0.1:60246 (4 >>> connections now open) >>> Sun Dec 16 11:43:11 [conn16372] end connection 127.0.0.1:60247 (3 >>> connections now open) >>> Sun Dec 16 11:43:11 [conn16374] end connection 127.0.0.1:60256 (2 >>> connections now open) >>> Sun Dec 16 11:43:11 [conn16373] end connection 127.0.0.1:60248 (2 >>> connections now open) >>> Sun Dec 16 11:43:11 [conn11044] end connection 127.0.0.1:54914 (1 >>> connection now open) >>> >>> Being a beginner with both Erlang and CB, I am a bit confused about >>> this. Maybe a problem with connection pooling? >>> >>> >>> Best regards, >>> Eugen >>> >>> >>> -- >>> >>> >>> >>> -- >> >> >> > > > > -- > Evan Miller > http://www.evanmiller.org/ > -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
