Haven't looked at InnoDB, but might have to take a look at it... Up until recently we haven't had any reason to doubt MyISAM, and it's served us well, in fact better than we need.
As for syslog - our MySQL logs to a .err file (nothing in syslog), and there's nothing in that file at all. It doesnt actually crash as such. It just starts running like a pig and eventually stopping accepting more connections (since each process hogs a slot, and doesnt seem to actually complete). The processes also start hogging all CPU time as well, in this "COPY to tmp table" state. Oh, and I believe that the Mandrake ISOs are un-patched. To my knowledge Mandrake have only released one public ISO set, and have kept the updates separately, rather than releasing a second ISO set with patches applied. On Tue, 28 Oct 2003, Chris Nolan wrote: > Get it fixed??!?!? And surrender? No, you can't do that! :-) > > Out of curiosity, have you guys looked at InnoDB for this purpose, given it > won't serialise writes? I take it you've seen MyISAM allowing readers to > continue while writes happen as adequate for what you need though? > > Additionally, and completely off-topic, do you know if those Mandrake 9.2 ISOs > have the 350MB or so of updates pre-applied? > > Regards, > > Chris > > P.S. Does syslog show anything unusual regarding your problem? I've been > lucky to never have a MySQL problem that I couldn't sovle by inspection, as > everything that gets written to syslog goes straight into a MySQL database! > :-) Of course, InnoDB having it's own logs helps quite a lot. > > On Tue, 28 Oct 2003 03:26 pm, Dan Goodes wrote: > > Hi Chris, > > > > On Tue, 28 Oct 2003, Chris Nolan wrote: > > > I just saw your mail address - you're one of the gurus who runs > > > PlanetMirror, aren't you? All hail he who provides my Mandrake ISOs! > > > Huzzah! :-) > > > > Yup - that would be us. Incidentally we've just flipped the bits on > > Mandrake 9.2, so you can download the ISO images now if you've been > > hanging out for it ;-) > > > > > Hmm....personally, I don't see how you can do "something wrong" during a > > > DELETE. This is one of those non-descript problems that give me sleepless > > > nights. > > > > Yes it is, and has caused me plenty of out-of-hours work so far trying to > > keep things sane and under control. I didn't think you could do anything > > wrong by upgrading a package either, but ouch, did it go wrong. > > > > > As you said, the RPMs aren't an option - may I ask why? > > > > Well, to be honest we've been building from source for some time, mainly > > to try to optimise MySQL and get rid of unneeded stuff like innodb support > > and so on. But having said that, I just had a word with my co-manager > > about the subject. We're about to do a roll-out of some new servers, and I > > want to trial running as much as possible from RPM, rather than source. > > > > > Additionally, there is a MySQL AB RPM available that has both the 4.0.x > > > and 3.23.x client libraries included. > > > > That would certainly prove useful. I am going to give it some serious > > thought (and testing) before we migrate to new gear. In the meantime I'm > > torn between going over the system and compeltely upgrading it, making > > sure to meet all dependencies and not stuff it up, and not upgrading it, > > finding out WHY its suddenly starting misbehaving and fixing it (or > > getting it fixed). > -- Regards, Dan Goodes : Systems Programmer : [EMAIL PROTECTED] Help support PlanetMirror - Australia's largest Internet archive by signing up for PlanetMirror Premium : http://planetmirror.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
