-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connections keep cycling #4
Comments
Mmmmm.... its get connected but it gets an error executing that is setting the flag to connection "unhealthy"... Could you emit the error, modifying the line 193 of the index.js file to include the err:
And post the error code? |
These are the error codes that set the connection as "unhealthy". At first glance, it looks correct. |
|
So I changed it to
Setting it to
|
This is that table's schema:
|
Wrapped it in a
|
Sorry for all the comments, just trying to also see what is up:
|
First conclusion: Error code 0x1000 (4096) is not a "fatal error". I will reproduce it tomorrow and try to fix it (you are more than welcome to send a pull request if you'ld like!) |
No problem, I will try to look at it in some more detail |
Hi, I will continue to try to reproduce it... |
Hi, The parsing needs to be changed to support this... |
I implemented partial data handling, I tested using 100K messages and it looks good! |
Sweet, thanks! I'm about to test this right now |
All I'm seeing now is:
One for every query - I've got about 1200+ that go async, but I'm just getting the above.. I'm able to connect with Thrift (I have a generic "driver" so I can swap). Binary protocol is enabled server-side... it's the same settings I had as before |
I added a write queue for sending the packets to the socket. async.times(100, function(n, next){
client.execute('select * from filters;', [], function (err, result) {/*...*/});
//do not wait until it is callback'ed
next();
});
//do not shutdown until all has been callback'ed :) Let me know if it works as expected. |
Yes, it's leaking fast! I was checking it the past few days. Thanks again for such great help!!!!!! |
Not a problem at all, glad I can help. I would try to be helping you fix Thanks for being so responsive!
|
Another one... could just be me doing something wrong again. The same code that basically was in the other bug.
This keeps cycling:
The text was updated successfully, but these errors were encountered: