Home › Forums › kdb+ › Query Routing/ Load Balancing / asynchronous callbacks › Re: Query Routing/ Load Balancing / asynchronous callbacks
-
I think the issue is that you are blocking on the client as your last command
x[]
Interprocess communication | Basics | kdb+ and q documentation – Kdb+ and q documentation (kx.com)
They may be no message being sent back from the client, especially true if is an issue on the server, or if you don’t have a callback on the calling handle.
Perhaps you meant to async flush?
neg[x][]
Might be worth while putting a nohup on the front of your ‘&’ commands, and I’d also suggest opening you handle as the projection, instead of opening per call to GW. You could add a check in your funct to check if the handle is valid and reopen as needed?
Just an note – you could save that function in any file, and source; doesn’t have to be .bashrc unless that’s your intention.