Ron Rothman
Ron Rothman
For any modern application that has to operate at scale, async is a must. I'll sketch out our own usage to illustrate. We run a web service that handles O(10,000)...
+1 for async client. We're processing many thousands of requests concurrently--are we supposed to block them all every time we call out to Aerospike?
Thanks Ronen, we appreciate your responsiveness and candor. Quick question: We noticed that the Python client does not release the GIL before calling out to Aerospike. Is this by design?...
Thanks, that's great. Our current (multiprocess) version has been quite stable but I'd certainly prefer to keep the entire client in-process. When 1.0.56 is released and I can find a...
Thanks Ronen. I spent this week porting our nonblocking client wrapper from gipc+multiprocess to gevent+threads+1.0.56. We've launched it and it's doing well so far. If it handles server hiccups gracefully...
You're calling `connect()` twice there; is that intentional? On Sun, Dec 13, 2015 at 11:56 PM, Joshua Buss [email protected] wrote: > Getting a segfault in the latest (1.0.57) and 1.0.56...
Thanks Ronen. Actually, I just wrote up a minimal example but it /did/ in fact stop when I hit CTRL-C. I'm looking into my original code now to see what...
Found it: it happens only when `concurrent=True`. Here's some code that demonstrates the problem (client v1.0.59). ``` python import aerospike from time import sleep client = aerospike.client({'hosts': ['localhost']}).connect() def cb_print((key,...
Thanks, will check and report back.
Bad news: problem still exists in client 2.0.1.