Intel ICC libs for Mysql 4.1 using libc 2.3
The Mysql download page says I need to install these libraries if I am using libc 2.3.x. I have a couple of questions: -- do I install them by just copying them to /usr/local/lib? -- will they play that silly game of running unoptimized code on AMD processors? -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Repeated corruption with MySQL 4.1.x using FULLTEXT indexes
I have an application where I create a faily large table (835MB) with a fulltext index. One of our development workstations and our production server will run the script to load the table, but afterwards we have a pervasive corruption, with out of range index index pointer errors. Oddly, my development workstation doesn't have those problems. My box and the ones having the problems have the following differences: - my box runs ReiserFS, the problem boxes run XFS - my box has a nice SCSI HD subsystem, the problem boxes do IDE. All three boxes run Linux 2.6.x kernels, and my workstation and production server share the same mobo. Come to think of it, I saw similar corruption issues under 2.4.x series kernels and MySQL v4.0.x, it just wasn't the show stopper it is now. Also, on all three boxes, altering the table to drop an index and create a new one requires a myisamchk -rq run afterwards when a fulltext index either exists or gets added or dropped, which I'd also call a bug. -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes
I've also found a problem with myisamchk --sort-keys: christopher:/var/lib/mysql/dmoz# myisamchk -rq xurls - check record delete-chain - recovering (with sort) MyISAM-table 'xurls' Data records: 1981904 - Fixing index 1 - Fixing index 2 - Fixing index 3 Data records: 4332227 christopher:/var/lib/mysql/dmoz# myisamchk -ce xurls Checking MyISAM file: xurls Data records: 4332227 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 - check data record references index: 3 - check records and index references christopher:/var/lib/mysql/dmoz# myisamchk -aS xurls - Sorting index for MyISAM-table 'xurls' christopher:/var/lib/mysql/dmoz# myisamchk -ce xurls Checking MyISAM file: xurls Data records: 4332227 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 - check data record references index: 3 myisamchk: error: Found key at page 208005120 that points to record outside datafile - check records and index references 1307000^C Also, I gt a segfault trying to use myisamchk --sort-records. Christopher L. Everett wrote: I have an application where I create a faily large table (835MB) with a fulltext index. One of our development workstations and our production server will run the script to load the table, but afterwards we have a pervasive corruption, with out of range index index pointer errors. Oddly, my development workstation doesn't have those problems. My box and the ones having the problems have the following differences: - my box runs ReiserFS, the problem boxes run XFS - my box has a nice SCSI HD subsystem, the problem boxes do IDE. All three boxes run Linux 2.6.x kernels, and my workstation and production server share the same mobo. Come to think of it, I saw similar corruption issues under 2.4.x series kernels and MySQL v4.0.x, it just wasn't the show stopper it is now. Also, on all three boxes, altering the table to drop an index and create a new one requires a myisamchk -rq run afterwards when a fulltext index either exists or gets added or dropped, which I'd also call a bug. -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes
Ed Lazor wrote: -Original Message- From: Christopher L. Everett [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 1:47 AM To: Mysql List Subject: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes I have an application where I create a faily large table (835MB) with a fulltext index. One of our development workstations and our production server will run the script to load the table, but afterwards we have a pervasive corruption, with out of range index index pointer errors. Oddly, my development workstation doesn't have those problems. My box and the ones having the problems have the following differences: - my box runs ReiserFS, the problem boxes run XFS - my box has a nice SCSI HD subsystem, the problem boxes do IDE. All three boxes run Linux 2.6.x kernels, and my workstation and production server share the same mobo. Come to think of it, I saw similar corruption issues under 2.4.x series kernels and MySQL v4.0.x, it just wasn't the show stopper it is now. Also, on all three boxes, altering the table to drop an index and create a new one requires a myisamchk -rq run afterwards when a fulltext index either exists or gets added or dropped, which I'd also call a bug. The problems you're describing are similar to what I've run into when there have been hardware related problems. One system had a problem with ram. Memory tests would test and report ram as ok, but everything started working when I replaced the ram. I think it was just brand incompatibility or something odd, because the ram never gave any problems in another system. I can generate the problem on much smaller data sets, in the mid tens of thousands of records rather than the millions of records. I'll do a memtest86 run on the development boxes overnight, but as I did that just after I installed linux on them and used the linux badram patch to exclude iffy sections of RAM, I don't think thats a problem. One system had hard drive media slowly failing and this wasn't obvious until we ran several full scan chkdsks. 3 hard drives all of different brand, model size, and the problem happening in the same place on both? Not likely. The funniest situation was where enough dust had collected in the CPU fan to cause slight over heating, which resulted in oddball errors. This isn't a problem on my box. I have a 1.5 pound copper heatsink with a 90mm heat sensitive fan and a fan+heatsink for the hard drive, and I saw myisamchk consistently generate the same error in the same place over and over. The sensors report my CPU running in the 45 degree centigrade range on my box pretty consistently. In each of these cases, everything would work fine until the system would start processing larger amounts of data. Small amounts of corruption began to show up that seemed to build on itself. This may or may not relate to what you're dealing with, but maybe it will help =) I'll look, but I don't think that's the problem. I'm going to see how small of a data set will cause this problem and file a bug report. -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Compiling from source
I'm using AMD K7 servers and don't need/want InnoDB so I want to compile mysql from source and I was curious about what compiler flags to use, so I went to http://www.mysql.com/doc/en/Compile_and_link_options.html which left me with some questions: 1. Does pgcc _still_ produce the fastest executables? I find this hard to believe when the pgcc download page at goof.com was last updated in 2000. 2. What compiler flags do the binaries distributed on www.mysql.com use? -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.1 replication relay log control
Victoria Reznichenko wrote: relay-log-purge is available from 4.1.1. Do you use 4.1.1 or 4.1.0? Is it in the manual because relay-log-purge is available in 4.0.x? AFAICT, 4.1.1 isn't available for download from the mysql.com site. 4.1.0-alpha is. How would one obtain 4.1.1? Would this work to manage the relay log size: 1. restart the slave server to make it start a new realy log 2. monitor the slave server status until we see that its on the new relay log 3. at that point stop the slave server again 4. delete the extra logs and edit the relay log index by hand. 5. start the slave server. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 4.1 replication relay log control
The online manual at http://www.mysql.com/doc/en/Replication_Options.html says that these two variables: max-relay-log-size=# relay-log-purge=0|1 exist to control the size of the relay log. But when I try to start my slave server with: set-variable = max-relay-log-size=192MB set-variable = relay-log-purge=1 in my.cnf it won't start. Am I using them right? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
ran out of space for bin logs
Aparrently my binlogs grew and grew and ate up all the space on their partition. At this point, I see this on the master mysql show master status; Empty set (0.00 sec) and this on the slave: mysql show slave status\G *** 1. row *** Master_Host: master-db Master_User: repl Master_Port: 3306 Connect_retry: 60 Master_Log_File: carbon-bin.09 Read_Master_Log_Pos: 201392116 Relay_Log_File: silicon-relay-bin.07 Relay_Log_Pos: 4 Relay_Master_Log_File: carbon-bin.09 Slave_IO_Running: No Slave_SQL_Running: Yes Replicate_do_db: Replicate_ignore_db: Last_errno: 0 Last_error: Skip_counter: 0 Exec_master_log_pos: 201392116 Relay_log_space: 4 which I think means my replications long past the point of retrieval. I'm pretty well reconciled to taking my system out of production, copying all the databases from the master to the slave, dropping the binlogs and restarting the replication. I have 2 questions: 1. Can I safely delete the binlogs and clear the binlog index by hand? 2. How can I regulate the size of the binlogs to something manageable? TIA for your help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Missing rows from select statements on heap table type
I upgraded from 3.23.27-beta to 3.23.32 after seeing bugfixes on intermediate versions. However the problems are continuing: Mod_perl DBI/DBD::mysql queries are failing to return rows that I know exist. It could be DBI/DBD::Mysql, but just in case I have some questions: - Are there known problems with the heap table type? - Are there better ways of programming, say using bindings rather than using '?' placeholders, that could help? - Could updates interfere with my queries to produce this? - What speed penalty would I incur by going to MyISAM tables, given enough RAM to keep the data I need in the filesystem cache? I don't think my server is particularly stressed, the load numbers are typically less than .3, .1, .05 and CPU 95% or better free. TIA for you help. -- Christopher Everett - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
