Re: hardware & clusters
Hello, If you have not already done so, check out the Cluster Eval Guide which has some tips which may assist you in your process. Much of the content was put together by the professional services group here at MySQL. http://www.mysql.com/why-mysql/white-papers/mysql_cluster_eval_guide.php Also, there is a cluster specific list: [EMAIL PROTECTED] Jimmy Guerrero Sr Product Manager MySQL, Inc Houston, TX Ricardo Oliveira wrote: Hi, As usual, everything is heavilly dependant on your specific scenario. Anyway, as a rule of thumb, databases benefit a LOT from RAM, and storage nodes benefit from I/O (more, faster disks). Regards, Ricardo -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 6.0.2-alpha and Falcon and possible bug/problem
I don't think that is the problem. I have been able to create over a 1,000,000 of tables with MySQL 5.1.21 and different storage engines with the same environment (I had already ulimit set). Thanks, Mariella Mathieu Bruneau <[EMAIL PROTECTED]> wrote: I never tried the falcon engine, but could it be that mysql is running out of file descriptor ? I think debian is limited to something around 8k per user by default. Check your pam settings and your ulimit ... Database usually use a lot of file handle and it's generally safe to increase it. Don't know if falcon use file handle per table or not tough... -- Mathieu Bruneau aka ROunofF === GPG keys available @ http://rounoff.darktech.org Mariella Petrini a �crit : > I have re-run and job and I was able to repeat the > problem. > Find attached the mysql server error log with all the > tarces. > > > Could you please help ? > > Thanks, > > Mariella > > > > --- Mariella Petrini > wrote: > >> Hi All, >> >> >> I have started using MySQL 6.0.2 with Falcon on >> Linux >> with Debian 4. >> I have compiled the source code for 64 bit >> executable. >> The system is an Intel 2 cpus 4 cores each, with 8 >> GB >> of RAM. >> >> I have started creating tables (without >> partitioning) >> whit engine type Falcon. After having created >> approximately 8,500 empty tables mysqld server was >> still alive, you could connect with the mysql >> client, >> but any command that you would type would freeze >> (never come back). >> >> I will try to re-run the same job, enabling >> falcon_debug_mask and see if I can get more info and >> repeat the problem. >> >> Mariella >> >> >> >> Below are shown the Falcon settings used: >> >> > +--+-+ >> >> | Variable_name| Value >> | >> > +--+-+ >> | falcon_checkpoint_schedule | 7 * * * * * >> | >> | falcon_debug_mask| 0 >> | >> | falcon_debug_server | OFF >> | >> >> | falcon_disable_fsync | OFF >> | >> >> | falcon_index_chill_threshold | 4 >> | >> >> | falcon_initial_allocation| 1073741824 >> | >> >> | falcon_max_transaction_backlog | 150 >> | >> >> | falcon_page_cache_size | 4194304 >> | >> | falcon_page_size | 4096 >> | >> | falcon_record_chill_threshold| 5 >> | >> | falcon_record_memory_max | 262144000 >> | >> >> | falcon_record_scavenge_floor | 50 >> | >> >> | falcon_record_scavenge_threshold | 67 >> | >> >> | falcon_scavenge_schedule | 15,45 * * * * * >> | >> >> | falcon_serial_log_buffers| 10 >> | >> >> | falcon_serial_log_dir| >> | >> | have_falcon | YES >> | >> > +--+-+ >> >> >> >> >> >> > >> Need a vacation? Get great deals >> to amazing places on Yahoo! Travel. >> http://travel.yahoo.com/ >> >> -- >> MySQL Internals Mailing List >> For list archives: http://lists.mysql.com/internals >> To unsubscribe: >> > http://lists.mysql.com/[EMAIL PROTECTED] >> > > > > > Shape Yahoo! in your own image. Join our Network Research Panel today! > http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 > > > > > > > - Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
Re: MySQL 6.0.2-alpha and Falcon and possible bug/problem
If Debian is limited to create files over 8k, it can be the reason of the problem. Falcon seems not create data file for tables, but still create ".frm" files for each tables. -- Jaemyung Kim 2007/9/9, Mathieu Bruneau <[EMAIL PROTECTED]>: > > I never tried the falcon engine, but could it be that mysql is running > out of file descriptor ? > > I think debian is limited to something around 8k per user by default. > Check your pam settings and your ulimit ... Database usually use a lot > of file handle and it's generally safe to increase it. Don't know if > falcon use file handle per table or not tough... > > -- > Mathieu Bruneau > aka ROunofF > > === > GPG keys available @ http://rounoff.darktech.org > > Mariella Petrini a écrit : > > I have re-run and job and I was able to repeat the > > problem. > > Find attached the mysql server error log with all the > > tarces. > > > > > > Could you please help ? > > > > Thanks, > > > > Mariella > > > > > > > > --- Mariella Petrini <[EMAIL PROTECTED]> > > wrote: > > > >> Hi All, > >> > >> > >> I have started using MySQL 6.0.2 with Falcon on > >> Linux > >> with Debian 4. > >> I have compiled the source code for 64 bit > >> executable. > >> The system is an Intel 2 cpus 4 cores each, with 8 > >> GB > >> of RAM. > >> > >> I have started creating tables (without > >> partitioning) > >> whit engine type Falcon. After having created > >> approximately 8,500 empty tables mysqld server was > >> still alive, you could connect with the mysql > >> client, > >> but any command that you would type would freeze > >> (never come back). > >> > >> I will try to re-run the same job, enabling > >> falcon_debug_mask and see if I can get more info and > >> repeat the problem. > >> > >> Mariella > >> > >> > >> > >> Below are shown the Falcon settings used: > >> > >> > > +--+-+ > >> > >> | Variable_name| Value > >> | > >> > > +--+-+ > >> | falcon_checkpoint_schedule | 7 * * * * * > >> | > >> | falcon_debug_mask| 0 > >> | > >> | falcon_debug_server | OFF > >> | > >> > >> | falcon_disable_fsync | OFF > >> | > >> > >> | falcon_index_chill_threshold | 4 > >> | > >> > >> | falcon_initial_allocation| 1073741824 > >> | > >> > >> | falcon_max_transaction_backlog | 150 > >> | > >> > >> | falcon_page_cache_size | 4194304 > >> | > >> | falcon_page_size | 4096 > >> | > >> | falcon_record_chill_threshold| 5 > >> | > >> | falcon_record_memory_max | 262144000 > >> | > >> > >> | falcon_record_scavenge_floor | 50 > >> | > >> > >> | falcon_record_scavenge_threshold | 67 > >> | > >> > >> | falcon_scavenge_schedule | 15,45 * * * * * > >> | > >> > >> | falcon_serial_log_buffers| 10 > >> | > >> > >> | falcon_serial_log_dir| > >> | > >> | have_falcon | YES > >> | > >> > > +--+-+ > >> > >> > >> > >> > >> > >> > > > > >> Need a vacation? Get great deals > >> to amazing places on Yahoo! Travel. > >> http://travel.yahoo.com/ > >> > >> -- > >> MySQL Internals Mailing List > >> For list archives: http://lists.mysql.com/internals > >> To unsubscribe: > >> > > http://lists.mysql.com/[EMAIL PROTECTED] > >> > > > > > > > > > Shape Yahoo! in your own image. Join our Network Research Panel > today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 > > > > > > > > > > > > > > > > > -- > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > >
Re: Master database server continues to crash
Are you running on a 32 bits architecture ? I have seen case where 1.7G is way too much for the total space mysql is allowed to use, especially if you have innodb buffer set to bigger than default value(8MB). Also you should check that the user is really allowed that size (ulimit). The duplicate for key is most certainly due to the crashing of mysql in the middle of the update of the key... Could it be different query on that server that makes it crashed ? Sorry don't know what to suggest really, it must be a real pain :( Regards Math aka ROunofF On Sat, Sep 08, 2007 at 06:30:08PM -0400, Matt Juszczak wrote: > Hi all, > > We've been having our master database server continually crash about once > or twice per week. The most recent output in the error log is contained at > the bottom of this message. > > The funny part is, that not only is mysql crashing often, but we are also > seeing some very weird errors in some of our queries... such as: > [nativecode=1062 ** Duplicate entry 'aa59442538' for key > That error comes from a query where the query actually has an ON DUPLICATE > KEY UPDATE clause. > > Also, we're getting errors with crashed tables: > Table '' is marked as crashed and should be repaired > > A check table on that table and other tables usually results in invalid row > count (these are MyISAM tables). There is no pattern to the errors other > than that they tend to occur on high traffic tables. > > We are running mysql version: > mysql Ver 14.12 Distrib 5.0.27 > > We are also running these mysql version elsewhere with no problems. I am > beginning to think more and more that this issue is related to the hardware > of the master server, not necessarilly the mysql version itself. > > Although we do need to upgrade, does anyone know of any existing bugs in > 5.0.27 that may be causing our issues? Or is this most likely a hardware > issue? > > Thanks, > > Matt > > > One of the outputs in the Error log (there are many more): > > Version: '5.0.27-standard-log' socket: '/var/lib/mysql/mysql.sock' port: > 3306 MySQL Community Edition - Standard (GPL) > 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=1073741824 > read_buffer_size=131072 > max_used_connections=19 > max_connections=300 > threads_connected=15 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = > 1701373 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x2ac0865b40 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > Cannot determine thread, fp=0x450c9f78, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x5f7374656c796568 > Stack trace seems successful - bottom reached > Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and > follow instructions on how to resolve the stack trac > e. Resolved > stack trace is much more helpful in diagnosing the problem, so please do > resolve it > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x2ac05362b0 is invalid pointer > thd->thread_id=15401 > The manual page at http://www.mysql.com/doc/en/Crashing.html contains > information that should help you find out what is causing the crash. > mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `"Pure virtual > method called." == "Aborted"' failed. > Fatal signal 6 while backtracing > > Number of processes running now: 0 > 070907 07:21:51 mysqld restarted > 070907 7:21:51 InnoDB: Database was not shut down normally! > > > -- > 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]
Master database server continues to crash
Hi all, We've been having our master database server continually crash about once or twice per week. The most recent output in the error log is contained at the bottom of this message. The funny part is, that not only is mysql crashing often, but we are also seeing some very weird errors in some of our queries... such as: [nativecode=1062 ** Duplicate entry 'aa59442538' for key That error comes from a query where the query actually has an ON DUPLICATE KEY UPDATE clause. Also, we're getting errors with crashed tables: Table '' is marked as crashed and should be repaired A check table on that table and other tables usually results in invalid row count (these are MyISAM tables). There is no pattern to the errors other than that they tend to occur on high traffic tables. We are running mysql version: mysql Ver 14.12 Distrib 5.0.27 We are also running these mysql version elsewhere with no problems. I am beginning to think more and more that this issue is related to the hardware of the master server, not necessarilly the mysql version itself. Although we do need to upgrade, does anyone know of any existing bugs in 5.0.27 that may be causing our issues? Or is this most likely a hardware issue? Thanks, Matt One of the outputs in the Error log (there are many more): Version: '5.0.27-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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=1073741824 read_buffer_size=131072 max_used_connections=19 max_connections=300 threads_connected=15 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1701373 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x2ac0865b40 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x450c9f78, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x5f7374656c796568 Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trac e. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x2ac05362b0 is invalid pointer thd->thread_id=15401 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. Fatal signal 6 while backtracing Number of processes running now: 0 070907 07:21:51 mysqld restarted 070907 7:21:51 InnoDB: Database was not shut down normally! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Different max_packet_size sizes
We've found recently that have a max packet size of 8 MB on our master and on our slaves causes problems. For some reason, slaves will error out during replication on packets that come from the master if they are very close to max_packet_size. The solution is to set the max_packet_size higher on the slaves than on the master, but we shouldn't have to do this (I don't think). Does replication add some sort of extra header information, etc. that would increase the packet sizes? If so, is there a formula for calculating what the max_packet_size should be in a master/slave/setup? Thanks, Matt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 6.0.2-alpha and Falcon and possible bug/problem
I never tried the falcon engine, but could it be that mysql is running out of file descriptor ? I think debian is limited to something around 8k per user by default. Check your pam settings and your ulimit ... Database usually use a lot of file handle and it's generally safe to increase it. Don't know if falcon use file handle per table or not tough... -- Mathieu Bruneau aka ROunofF === GPG keys available @ http://rounoff.darktech.org Mariella Petrini a écrit : I have re-run and job and I was able to repeat the problem. Find attached the mysql server error log with all the tarces. Could you please help ? Thanks, Mariella --- Mariella Petrini <[EMAIL PROTECTED]> wrote: Hi All, I have started using MySQL 6.0.2 with Falcon on Linux with Debian 4. I have compiled the source code for 64 bit executable. The system is an Intel 2 cpus 4 cores each, with 8 GB of RAM. I have started creating tables (without partitioning) whit engine type Falcon. After having created approximately 8,500 empty tables mysqld server was still alive, you could connect with the mysql client, but any command that you would type would freeze (never come back). I will try to re-run the same job, enabling falcon_debug_mask and see if I can get more info and repeat the problem. Mariella Below are shown the Falcon settings used: +--+-+ | Variable_name| Value | +--+-+ | falcon_checkpoint_schedule | 7 * * * * * | | falcon_debug_mask| 0 | | falcon_debug_server | OFF | | falcon_disable_fsync | OFF | | falcon_index_chill_threshold | 4 | | falcon_initial_allocation| 1073741824 | | falcon_max_transaction_backlog | 150 | | falcon_page_cache_size | 4194304 | | falcon_page_size | 4096 | | falcon_record_chill_threshold| 5 | | falcon_record_memory_max | 262144000 | | falcon_record_scavenge_floor | 50 | | falcon_record_scavenge_threshold | 67 | | falcon_scavenge_schedule | 15,45 * * * * * | | falcon_serial_log_buffers| 10 | | falcon_serial_log_dir| | | have_falcon | YES | +--+-+ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ -- MySQL Internals Mailing List For list archives: http://lists.mysql.com/internals To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 6.0.2-alpha and Falcon and possible bug/problem
I have re-run and job and I was able to repeat the problem. Find attached the mysql server error log with all the tarces. Could you please help ? Thanks, Mariella --- Mariella Petrini <[EMAIL PROTECTED]> wrote: > Hi All, > > > I have started using MySQL 6.0.2 with Falcon on > Linux > with Debian 4. > I have compiled the source code for 64 bit > executable. > The system is an Intel 2 cpus 4 cores each, with 8 > GB > of RAM. > > I have started creating tables (without > partitioning) > whit engine type Falcon. After having created > approximately 8,500 empty tables mysqld server was > still alive, you could connect with the mysql > client, > but any command that you would type would freeze > (never come back). > > I will try to re-run the same job, enabling > falcon_debug_mask and see if I can get more info and > repeat the problem. > > Mariella > > > > Below are shown the Falcon settings used: > > +--+-+ > > | Variable_name| Value > | > +--+-+ > | falcon_checkpoint_schedule | 7 * * * * * > | > | falcon_debug_mask| 0 > | > | falcon_debug_server | OFF > | > > | falcon_disable_fsync | OFF > | > > | falcon_index_chill_threshold | 4 > | > > | falcon_initial_allocation| 1073741824 > | > > | falcon_max_transaction_backlog | 150 > | > > | falcon_page_cache_size | 4194304 > | > | falcon_page_size | 4096 > | > | falcon_record_chill_threshold| 5 > | > | falcon_record_memory_max | 262144000 > | > > | falcon_record_scavenge_floor | 50 > | > > | falcon_record_scavenge_threshold | 67 > | > > | falcon_scavenge_schedule | 15,45 * * * * * > | > > | falcon_serial_log_buffers| 10 > | > > | falcon_serial_log_dir| > | > | have_falcon | YES > | > +--+-+ > > > > > > > > Need a vacation? Get great deals > to amazing places on Yahoo! Travel. > http://travel.yahoo.com/ > > -- > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: seoparator help
Thanks for the help i have got it correct. -- View this message in context: http://www.nabble.com/seoparator-help-tf4316769.html#a12568601 Sent from the MySQL - General mailing list archive at Nabble.com. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
