Re: MySQL 4.0.16 on RHEL3 AS IA64
We were unsuccessful getting the MySQL AMD64 rpms to work on RHEL3 AS. I downloaded the source rpm and rebuilt the rpms on our Opteron server and they have mostly worked, only one crash so far which we are in the process of reporting to the MySQL support group. Of course, we are experiencing some serious sadness with the RANGE vs REF optimization bug, but I am hopeful that when 4.0.17 comes out all will be well again. Tomek Dudziak wrote: Hi, Did anyone get the 4.0.16 binary to work on RedHat 3 Enterprise for IA64? I read that the same happens on RH3AS for AMD64. This was thoroughly tested with our production team and it works truly just fine. according to MySQL support :-\ 031102 22:07:17 mysqld started mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 031102 22:07:17 mysqld ended -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.0.16 on RHEL3 AS AMD64
I should sleep before posting, I suppose. I suppose this is the issue with the NPTL threads library? If so, has anyone dealt with that issue with MySQL? I remember hearing that perhaps using a dynamically linked mysqld would work around the problem. Owen Owen Scott Medd wrote: I have Red Hat Enterprise Linux 3 AS installed on a dual Opteron server with 16GB of memory (hoping to solve innodb_buffer_pool size issues under x86). I upgraded the MySQL included with RHEL3 (3.23.58) to the 4.0.16 rpms from the MySQL website. I had thought this would be a piece of cake, as we're running 4.0.16 in production with very few issues. However, when starting the upgraded MySQL on the Opteron server, I get a segmentation fault. Anyone have any actual experience with this configuration? I had to physically remove the 3.23.58 packages (and the packages dependent on them), doing an upgrade did not fly with the rpm dependencies. I don't really have an option of going back to 3.23.58, as I have post-4.0.14 innodb data. 031102 22:07:17 mysqld started mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 031102 22:07:17 mysqld ended -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.0.16 on RHEL3 AS AMD64
It doesn't look like it is *that* easy. It looks like the server starts when using mysqld-max, I just have to get the mysql database tables built and see how it goes from there (being lazy and using the rpms I don't get those tables as it uses the mysqld server... similar issues with mysql_install_db utility, it appears). Perhaps innodb versions 4.0.16 and 3.23.58 (which is what RedHat ships in RHEL3) are compatible so my innodb data files won't choke when I take them back to 3.23.58? But then there are the my.cnf variable name changes... It would be simpler to be able to run the current software. I will report back with my later findings. Thanks, Owen [EMAIL PROTECTED] wrote: Hiya, tried LD_ASSUME_KERNEL=2.2.5? See here: http://sources.redhat.com/ml/libc-hacker/2003-06/msg00032.html May work, then again your machine may blow up! So use at your own risk as I am guessing! Greg -Original Message- From: Owen Scott Medd [mailto:[EMAIL PROTECTED] Sent: 03 November 2003 15:08 To: [EMAIL PROTECTED] Subject: Re: MySQL 4.0.16 on RHEL3 AS AMD64 I should sleep before posting, I suppose. I suppose this is the issue with the NPTL threads library? If so, has anyone dealt with that issue with MySQL? I remember hearing that perhaps using a dynamically linked mysqld would work around the problem. Owen Owen Scott Medd wrote: I have Red Hat Enterprise Linux 3 AS installed on a dual Opteron server with 16GB of memory (hoping to solve innodb_buffer_pool size issues under x86). I upgraded the MySQL included with RHEL3 (3.23.58) to the 4.0.16 rpms from the MySQL website. I had thought this would be a piece of cake, as we're running 4.0.16 in production with very few issues. However, when starting the upgraded MySQL on the Opteron server, I get a segmentation fault. Anyone have any actual experience with this configuration? I had to physically remove the 3.23.58 packages (and the packages dependent on them), doing an upgrade did not fly with the rpm dependencies. I don't really have an option of going back to 3.23.58, as I have post-4.0.14 innodb data. 031102 22:07:17 mysqld started mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 031102 22:07:17 mysqld ended -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 4.0.16 on RHEL3 AS AMD64
I have Red Hat Enterprise Linux 3 AS installed on a dual Opteron server with 16GB of memory (hoping to solve innodb_buffer_pool size issues under x86). I upgraded the MySQL included with RHEL3 (3.23.58) to the 4.0.16 rpms from the MySQL website. I had thought this would be a piece of cake, as we're running 4.0.16 in production with very few issues. However, when starting the upgraded MySQL on the Opteron server, I get a segmentation fault. Anyone have any actual experience with this configuration? I had to physically remove the 3.23.58 packages (and the packages dependent on them), doing an upgrade did not fly with the rpm dependencies. I don't really have an option of going back to 3.23.58, as I have post-4.0.14 innodb data. 031102 22:07:17 mysqld started mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 031102 22:07:17 mysqld ended -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Master/Master Replication
Well, not logically valid in the general sense (in that naive master-master replication can be self-destructive) but can be extremely useful when utilized knowing all the limitations and potential pitfalls. On Sun, 2003-08-31 at 10:01, Douglas Granzow wrote: I think the message they were trying to convey in the answer is two-way replication will result in data corruption and therefore should not be used. Consider a table with an AUTO_INCREMENT id field. If two different inserts are done simultaneously, one on each master, both will get the same id number. For example: client A connects to master 1 and does INSERT INTO TABLE VALUES (NULL, 7, 8, 9) client B connects to master 2 and does INSERT INTO TABLE VALUES (NULL, 9, 8, 7) on master 1, the table looks like this: +---+---+---+---+ | 1 | 7 | 8 | 9 | +---+---+---+---+ on master 2, the table looks like this: +---+---+---+---+ | 1 | 9 | 8 | 7 | +---+---+---+---+ Now, the insert from master 1 gets replicated to master 2 -- but master 2 gives this insert a different AUTO_INCREMENT number. Master 2 now looks like this: +---+---+---+---+ | 1 | 9 | 8 | 7 | | 2 | 7 | 8 | 9 | +---+---+---+---+ And finally, the insert from master 2 gets replicated to master 1, again with different results. Master 1 now looks like this: +---+---+---+---+ | 1 | 7 | 8 | 9 | | 2 | 9 | 8 | 7 | +---+---+---+---+ As you can see, you have two tables which are supposedly replicated, but neither matches the other. It may be technically possible to set up MySQL to make it appear to have a master-master replication configuration, but such a configuration would not be logically valid. --- Emi Nelson [EMAIL PROTECTED] wrote: Hello, I have set up a master/slave replication environment using 4.0.13 but would like to know if there is a way to set up master/master replication between two databases, both able to be inserted/updated/deleted, tables created, etc., with the changes on both databases propagated to each other. I see one comment in the documentation on two way replication: Q: What issues should I be aware of when setting up two-way replication? A: MySQL replication currently does not support any locking protocol between master and slave to guarantee the atomicity of a distributed (cross-server) update. In other words, it is possible for client A to make an update to co-master 1, and in the meantime, before it propagates to co-master 2, client B could make an update to co-master 2 that will make the update of client A work differently than it did on co-master 1. Thus when the update of client A will make it to co-master 2, it will produce tables that will be different from what you have on co-master 1, even after all the updates from co-master 2 have also propagated. So you should not co-chain two servers in a two-way replication relationship, unless you are sure that you updates can safely happen in any order, or unless you take care of mis-ordered updates somehow in the client code. You must also realise that two-way replication actually does not improve performance very much, if at all, as far as updates are concerned. Both servers need to do the same amount of updates each, as you would have one server do. The only difference is that there will be a little less lock contention, because the updates originating on another server will be serialised in one slave thread. This benefit, though, might be offset by network delays. -- But there is no further info on how to set it up. Is bidrectional set up by using the log-slave-updates parameter on the slave and point it to the 'master'? It's just kind of vague :-( Thanks in advance, Emi -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: malloc'ing 2GB+ of memory in mysql
I know we are facing this same question right now (I have 8 way servers with 16GB of memory running MySQL, with 5 GB sitting unused while the poor innodb buffer pool sits starved for memory). Do we replace these servers with 4 way Opterons (are there 8 ways promised yet?) or is there another answer? In particular, what is involved with being a feature sponsor? (lol... show me the money, eh?). And, more importantly, have you done any estimates about how long it would take to implement AWE in the RedHat AS environment (which happens to be our environment too)? Curious, Owen On Wed, 4 Jun 2003, Heikki Tuuri wrote: Per, I remember someone also reporting a problem that glibc or Linux does not allow creation of new threads if one has allocated = 2 GB user memory. I think there are problems in where the OS places the excutable, thread stacks, etc. So it is uncharted territory. Oracle seems to have an option to use AWE memory on the Red Hat Advanced Server. Then the limit is 64 GB on a 32-bit Intel processor. InnoDB-4.1 has the same AWE option, but only on certain Windows versions. If Itanium and Opteron fail to take off, or a feature sponsor appears, I may consider implementing AWE also on Linux. The memory crunch is getting so severe that I believe some 64-bit processor must become common by 2005. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Transactions, foreign keys, and a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ - Original Message - From: Per Andreas Buer [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Wednesday, June 04, 2003 1:21 PM Subject: malloc'ing 2GB+ of memory in mysql Hi The Mysql binary distribution for IA32-linux is statically linked with glibc. glibc malloc limits memory allocations to 2GB, which means that a buffer in mysql can't grow beyond 2GB. This is due to some paranoia in glibc malloc - they don't rely on the size to be an unsigned int - which limits the size to 2^31 on any 32-bit platform. Has anyone tried to remove this limit in glibc malloc or linking Mysql with another malloc implementation? -- Per Andreas Buer -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- USMail: InterGuide Communications, 230 Lyn Anne Court, Ann Arbor, MI 48103 phone:+1 734 997-0922 fax:+1 734 661-0324 mailto:[EMAIL PROTECTED]http://www.interguide.com/~osm/ [ Sometimes wrong. Never in doubt. ] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld Threads with Innobase
[ start stupid question ] Does setting innodb_thread_concurrency to 1 imply that only one innodb thread will be working at any given time? So using this on SMP servers that you would like to be answering simultaneous queries is probably not what you would really like to be doing, no? [ end stupid question ] Owen On Wed, 2002-10-09 at 02:55, Heikki Tuuri wrote: Nicholas, - Original Message - From: Nicholas Gaugler [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Wednesday, October 09, 2002 8:22 AM Subject: mysqld Threads with Innobase I know it's not very important in normal day to day operations, but does anyone know what each thread does within mysqld with Innobase installed? It'd be nice to know what Innobase is doing when a process is pinned at 100% of the cpu..if it's doing cleanup from a huge update, etc. /usr/local/sqldrive/mysql-4.0.4-beta/bin/mysqld --defaults-extra-file=/usr/l ocal/sqldrive/mysql-4.0.4-beta/data/my 1682 ttyp1S 0:00 /usr/local/sqldrive/mysql-4.0.4-beta/bin/mysqld --defaults-extra-file=/usr/l ocal/sqldrive/mysql-4.0.4-beta/data/my ... only one thread, the main thread, does background cleaning operations. You can see from SHOW INNODB STATUS what the main thread is currently doing. It is a good idea to tell the id of that thread in the printout of SHOW INNODB STATUS. I will add it to 4.0.5. In your case there are lots of threads eating up 100 % of CPU. If the performance is very slow, this looks like yet another case of Linux 'thread thrashing' which is plaguing both MyISAM and InnoDB tables under certain loads. It is a clear performace bug in Linux or glibc, and we are working to find a fix or a workaround to that problem. You can try setting set-variable = innodb_thread_concurrency = 1 in my.cnf to remove the thread thrashing. That helps in some cases Thanks! nickg Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - 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 -- USMail: InterGuide Communications, 1611 Dexter Avenue, Ann Arbor, MI 48103 Phone:+1 734 997-0922 FAX:+1 734 661-0324 mailto:[EMAIL PROTECTED] http://www.interguide.com/~osm/ - 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
Re: Can you convert a MS Sql database to MySQL?
Actually, we are looking to do just the same thing for a pretty large database. We've come across a project at sourceforge that claims to do this (upsize bcp) and will be investigating how well it works next week. Sourceforge page is http://sourceforge.net/projects/upsize-bcp/. On Fri, 13 Apr 2001, AJ wrote: Does anyone know any good source of info for the conversion of MS Sql databases to MySql? Perhaps a prog that does this? Thanks for any information in advance, AJ Workman - 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 - 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
Re: Provider claims 'it's normal that mysql crashes', is that true?
We've been running on RedHat distribution (starting with 5.2 or so) and Slackware before that for the last few years (currently running mysql 3.23.32... that update bug introduced in 3.23.34 really spanked us hard, we'll be moving to "latest" again soon). Currently, we've got dual and quad PII and PIII machines with upwards of 2GB of memory averaging around 400 queries/second (150-400 sessions at any given time). Our mysql uptime depends on how often we do software or hardware upgrades, not on mysql "mean time to crash". Translated: our mysql servers run for weeks/months. I consider our mysql databases to be very stable. :) Owen On Wed, 4 Apr 2001, Gunnar von Boehn wrote: Hello My provider 11-Puretec (www.puretec.de) hosting more than 1.000.000 domains runs about 14 Databaseserver with MySQL 3.22.32-log on Linux dual Penti-III 500Mhz machines. In the last 6 month the average uptime of the mysql-servers was around 8 hours. As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Is that true? regards Gunnar von Boehn - 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 -- USMail: CareerSite Corporation, 310 Miller Avenue, Ann Arbor, MI 48103 Phone:+1 734 213-9500 FAX:+1 734 213-9011 mailto:[EMAIL PROTECTED] http://www.careersite.com/~osm/ - 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
