My apologies for sending the same message again, but in the first try it did create a completely new thread.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Mike, Thanks for your feedback and sorry for taking so long to reply, but somehow the email did not make it to my mailbox (corporate spam filter I suppose). I'm copy-pasting your response, so let's hope it does not screw the thread. The OS is SUSE Linux Enterprise Server 11 SP2 (x86_64) and we did not see any hardware related problems on the machine (I/O, network, ...) We took your advice and increased the log level and indeed we saw quite some things to work with. Forest::insert: SwocUxOnlineContent-06 XDMP-INMMLISTFULL: In-memory list storage full; list: table=78%, wordsused=76%, wordsfree=0%, over head=24%; tree: table=56%, wordsused=53%, wordsfree=47%, overhead=1% And after that one, several client connection problems (No XDQP session): 2013-02-06 14:40:37.049 Debug: Stopping XDQPClientConnection, server=ml-c1-u2.swets.nl /data/everwisedata3/Forests/SwocUxOnlineContent-06/ We did check the documentation and bumped the in-memory-list-size from 512 to 1024. For around one hour the problems seemed to be solved, although after a while the hung messages reappeared. Now I'm seeing this in the system logs, which I think it may be related (not sure if it's a symptom or the root cause): Jan 31 17:41:46 ml-c1-u3 kernel: [17467686.201893] TCP: Possible SYN flooding on port 7999. Sending cookie 7999 is the defined bind port for the 3 machines of our cluster, and after checking with netstat only the other 2 are trying to connect on that port. Any other tips? Regards, Miguel _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
