G
Database Security. Database Auditing. Database Caching. Database Masking. Get it nowgreensql-fw dies with large results
Posted December 19th, 2008 by ramp
in
Hello,
I've been playing around with greensql for the last 2 days, and we have run into a strange problem.
greensql-fw sometimes dies when the query result contains a large amount of rows in combination with a large amount of columns. Sometimes it does not return the data at all instead of dying, and at other times it works fine.
This behavior happens in multiple modes, including simulaton.
Is there a filter or special restriction I'm missing which disables this behavior ? Or is there a hard cap somewhere.
Comments
Hello Ramp Just give me an
Hello Ramp
Just give me an example of the query that kills the application. I will try to trace it and find what's going wrong.
Regarding empty result set, it sound like this GreenSQL found query that has something wrong in it.
Check the management tool. You will find the explanation.
Best regards,
Yuli
Please check the version
Please check the version available in sourceforge (using svn).
It is possible that all your bugs were fixed.
PS. Here you can find directions how to get application using svn:
http://www.greensql.net/node/113
Sorry for bringing up this
This comment has been moved here.
With 1.0 all my crashing
With 1.0 all my crashing problems disappeared, it ran without a crash since I updated from the 0.x till I tried to update to 1.2
Unfortunately 1.2 runs at 100% cpu on one core for some reason on my live machine, so I ended up downgrading again to 1.0.
Hello Can you provide more
Hello
Can you provide more details about your production server - linux version you use, CMS software you use so we can try to reproduce this error here ?
Thanks,
Yuli
Centos 5.4 / 64 bit We use
Centos 5.4 / 64 bit
We use an inhouse written cms in php, mysql has an avg qps of 440, hence it might be difficult to replicate. 1.0 runs fine, 1.2 maxes out one cpu core,
What other information do you need which can be of help?