I often occur a case when there are many simultaneous requests to kdb server (more than 30), it deadlocks and stops responding until some connections are closed down. Is there a way to avoid this problem by running KDB with multithreading or other optjon?
http://code.kx.com/wiki/Cookbook/MultithreadedInputMode
Multithreaded input queue mode is active when the port for incoming connections is specified as negative, e.g. for startup
q -p -5000
Restrictions -
.z.W and async messaging should not be used in this mode.
Hi Sam,
A couple of questions - apologies if this rehashes old ground that you have already gone over. Are you sure it is a deadlock - asuming you are running linux, this should be relatively easy to check - strace, or something less invasive perhaps. It is not an issue with the number of concurrent pids (fix by tweaking the kernel settings)? Is this happening with async communication, deferred sync, or is there sync communication involved too?
Cheers,
Andy
They say it is not to be used for reading data from disk. So this is not an option for hosting large tick database from server. Am I missing something?
this is not a known issue; it should be fine. Please describe the steps/scenario to reproduce the problem.
thanks