We don't use PHP to talk to Cassandra directly. But we do have the front-end communicate to our backend services which are over Thrift. We've used Framed and Buffered, both required some tweaks. We use the PHP C-extension from the Thrift repo. I have to admit, it's pretty crappy, we had to make some modifications in Thrift.
I opened this ticket, I need to submit some of my patches so we can close it out (resolve the time out issues): https://issues.apache.org/jira/browse/THRIFT-638 -Chris On Apr 22, 2010, at 9:03 AM, S Ahmed wrote: > If digg uses PHP with cassandra, can the library really be that old? > > Or they are using their own custom php cassandra client? (probably, but just > making sure). > > On Fri, Apr 16, 2010 at 2:13 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Fri, Apr 16, 2010 at 12:50 PM, Lee Parker <l...@socialagency.com> wrote: > > Each time I start it up, it will > > work fine for about 1 hour and then it will crash the servers. The error > > message on the servers is usually an out of memory error. > > Sounds like > http://wiki.apache.org/cassandra/FAQ#slows_down_after_lotso_inserts > to me. > > > I will get > > several time out errors on the clients > > Symtomatic of running out of memory. > > > and occasionally get an error telling > > me that i was missing the timestamp. > > This is an entirely different problem. Your client is sending > garbage, plain and simple. Why that is, I don't know. The PHP Thrift > binding is virtually unmaintained, so it could be a bug there, but > Digg uses PHP against Cassandra extensively and hasn't hit this to my > knowledge. As I said in another thread, I wouldn't rule out bad > hardware. > > > The timestamp error is accompanied by > > a server crashing if I use framed transport instead of buffered. > > Thrift is fragile when the client sends it garbage. > (https://issues.apache.org/jira/browse/THRIFT-601) > > > One of the reasons we > > were trying cassandra was to scale out with smaller nodes rather than having > > to run larger instances for mysql. > > 2 x 1GB isn't a whole lot to do a bulk load with. You may have to > throttle your clients to fix the OOM completely. > > -Jonathan >
