puzzled issue for deadlock due to locking upgrade from LOCK_S to LOCK_X
Hi Guys, I got a deadlock problem, and it puzzled me days. Hope some body could help with some explanation for the reason of deadlock, better if some extra advises. * * *DeadLock Info:* * * - - - (1) TRANSACTION: TRANSACTION 13D947E32, ACTIVE 0 sec, process no 10928, OS thread id 1470925120 starting index read mysql tables in use 1, locked 1 LOCK WAIT 5 lock struct(s), heap size 1248, 3 row lock(s), undo log entries 1 MySQL thread id 2343068, query id 874146900 xxx.yyy.zzz.183 feel Updating UPDATE feed_daily_sum_1124 SET gmt_modified = now() ,GOOD_SELLER = IFNULL(GOOD_SELLER,0)+1 WHERE USER_ID = 376169572 AND RATEDATE = '2011-11-28 00:00:00' - (1) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 704 page no 220 n bits 736 index `uk_daily_sum_userid` of table `feel_17`.`feed_daily_sum_1124` trx id 13D947E32 lock_mode X locks rec but not gap waiting Record lock, heap no 537 PHYSICAL RECORD: n_fields 3; compact format; info bits 0 0: len 8; hex 8000166be464; asc k d;; 1: len 3; hex 8fb77c; asc |;; 2: len 8; hex 443449df; asc D4I ;; - - - (2) TRANSACTION: TRANSACTION 13D947E3B, ACTIVE 0 sec, process no 10928, OS thread id 1538029888 starting index read, thread declared inside InnoDB 500 mysql tables in use 1, locked 1 5 lock struct(s), heap size 1248, 3 row lock(s), undo log entries 1 MySQL thread id 2309035, query id 874146901 xxx.yyy.zzz.56 feel Updating UPDATE feed_daily_sum_1124 SET gmt_modified = now() ,GOOD_SELLER = IFNULL(GOOD_SELLER,0)+1 WHERE USER_ID = 376169572 AND RATEDATE = '2011-11-28 00:00:00' - (2) HOLDS THE LOCK(S): RECORD LOCKS space id 704 page no 220 n bits 736 index `uk_daily_sum_userid` of table `feel_17`.`feed_daily_sum_1124` trx id 13D947E3B lock mode S Record lock, heap no 537 PHYSICAL RECORD: n_fields 3; compact format; info bits 0 0: len 8; hex 8000166be464; asc k d;; 1: len 3; hex 8fb77c; asc |;; 2: len 8; hex 443449df; asc D4I ;; - - - (2) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 704 page no 220 n bits 736 index `uk_daily_sum_userid` of table `feel_17`.`feed_daily_sum_1124` trx id 13D947E3B lock_mode X locks rec but not gap waiting Record lock, heap no 537 PHYSICAL RECORD: n_fields 3; compact format; info bits 0 0: len 8; hex 8000166be464; asc k d;; 1: len 3; hex 8fb77c; asc |;; 2: len 8; hex 443449df; asc D4I ;; - - - WE ROLL BACK TRANSACTION (2) TRANSACTIONS *Problem:* * * It's a typical deadlock problem, and the two SQL shown are the same. uk_daily_sum_userid is the index that contains user_id and ratedate. Seen from the innodb provided information, we could deduce that: T1 Waiting for a LOCK_X for Record R1 T2 Hods a LOCK_S of Record R1, and waiting for a LOCK_X for R1 As T2 needs a lock upgrade but that is a LOCK_X waiting before T2 requests LOCK_X for the same record, that caused the deadlock. OK, it's all ok for me to understand the deadlock from innodb deadlock info. But my question is: WHY LOCK_S is existed in T2? Let's me show you the SQL in Transaction. T1 and T2 are the same logic SQL assembles as: sql1: INSERT INTO feed_receive values (xxx, yyy); sql2: UPDATE feed_daily_sum sql3: UPDATE feed_all_sum sql4: commit There is no FK constrains in the three tables, all are depended tables!!! WHY LOCK_S should occur in this case? For my understanding of LOCK_S, FK contains (update child but parent related record should have LOCK_S), or SELECT xxx LOCK in shared mode. Any idea?
Tables are lost for DDL and different behaviors for alter table failed situation between innobase and innodb_plugin
*summary:*
Recently we hit lost tables during DDL for online products, and after some
observersion, we found some interesting hehaviors if fil_rename_tablespace
failed as retry 25.
That might be another issue that not discussed here.
THERE MUST BE SINGLE TABLESPACE
Here is the steps to show the behavior:
*1. compile 5.1.48 source code.*
CFLAGS=-O0 -g CXX=gcc CXXFLAGS=-O0 -g -felide-constructors \
-fno-exceptions -fno-rtti
export CFLAGS CXXFLAGS
./configure --with-plugins=innodb_plugin
make -j32
*2. debug with plugin innodb*
2.1 # attach a running pid
(gdb) b fil_rename_tablespace
Breakpoint 1 at 0x2abfed30: file fil/fil0fil.c, line 2435.
(gdb) c
Continuing.
[Switching to Thread 0x4944a940 (LWP 7069)]
Breakpoint 1, fil_rename_tablespace (old_name=0xeacdc20 sbtest/sb1, id=51,
new_name=0xea96fa0 sbtest/#sql2-1b8b-1) at fil/fil0fil.c:2435
2435{
(gdb) c
Continuing.
Breakpoint 1, fil_rename_tablespace (old_name=0xeabb3f0
sbtest/#sql-1b8b_1, id=52, new_name=0xea96fa0 sbtest/sb1) at
fil/fil0fil.c:2435
2435{
(gdb) return 0
Make fil_rename_tablespace return now? (y or n) y
#0 0x2abea8c4 in dict_table_rename_in_cache (table=0xeabb288,
new_name=0xea96fa0 sbtest/sb1,
rename_also_foreigns=1) at dict/dict0dict.c:951
951 } else if (!fil_rename_tablespace(old_name,
table-space,
(gdb)
(gdb) l
946 fputs( (, stderr);
947 ut_print_filename(stderr,
948
table-dir_path_of_temp_table);
949 fputs( )\n, stderr);
950 return(FALSE);
951 } else if (!fil_rename_tablespace(old_name,
table-space,
952 new_name)) {
953 return(FALSE);
954 }
955 }
(gdb) finish
Run till exit from #0 0x2abea8c4 in dict_table_rename_in_cache
(table=0xeabb288, new_name=0xea96fa0 sbtest/sb1, rename_also_foreigns=1)
at dict/dict0dict.c:951
0x2ac6527e in row_rename_table_for_mysql (old_name=0xea97000
sbtest/#sql-1b8b_1, new_name=0xea96fa0 sbtest/sb1, trx=0xeacf728,
commit=1)
at row/row0mysql.c:3905
3905if (!dict_table_rename_in_cache(table, new_name,
Value returned is $1 = 0
(gdb) l
3900trx-error_state = DB_SUCCESS;
3901} else {
3902/* The following call will also rename the .ibd data
file if
3903the table is stored in a single-table tablespace */
3904
3905if (!dict_table_rename_in_cache(table, new_name,
3906!new_is_tmp)) {
3907trx-error_state = DB_SUCCESS;
3908trx_general_rollback_for_mysql(trx, NULL);
3909trx-error_state = DB_SUCCESS;
(gdb) l
3910goto funct_exit;
3911}
3912
3913/* We only want to switch off some of the type
checking in
3914an ALTER, not in a RENAME. */
3915
3916err = dict_load_foreigns(
3917new_name, !old_is_tmp ||
trx-check_foreigns);
3918
3919if (err != DB_SUCCESS) {
(gdb) finish
Run till exit from #0 0x2ac6527e in row_rename_table_for_mysql
(old_name=0xea97000 sbtest/#sql-1b8b_1, new_name=0xea96fa0 sbtest/sb1,
trx=0xeacf728, commit=1) at row/row0mysql.c:3905
0x2ac14e0b in ha_innodb::rename_table () from
/u01/mysql-5.1.48/storage/innodb_plugin/.libs/ha_innodb_plugin.so
Value returned is $2 = 10
2.2 here is the key routines:
storage/innodb_plugin/row/row0mysql.c: row_rename_table_for_mysql
3905 if (!dict_table_rename_in_cache(table, new_name,
3906 !new_is_tmp)) {
3907 trx-error_state = DB_SUCCESS;
3908 trx_general_rollback_for_mysql(trx, NULL);
3909 trx-error_state = DB_SUCCESS;
3910 goto funct_exit;
3911 }
2.3 client's output:
root@sbtest 05:00:24alter table sb1 add column d2 int;
Query OK, 0 rows affected (9 min 47.97 sec)
Records: 0 Duplicates: 0 Warnings: 0
root@sbtest 05:11:26desc sb1;
ERROR 1146 (42S02): Table 'sbtest.sb1' doesn't exist
*3. different code between innodb and plugin*
3.1 innodb add err = DB_ERROR; before goto funct_exit; when
dict_table_rename_in_cache failed.
3.2 test innodb work and result could be refered to modified innodb plugin
just like innobase behavior, add err = DB_ERROR; before exit
3905 if (!dict_table_rename_in_cache(table, new_name,
3906 !new_is_tmp)) {
3907 trx-error_state = DB_SUCCESS;
3908 trx_general_rollback_for_mysql(trx, NULL);
3909
mysql tables are lost for DDL of alter table .. add column ...
mysql tables are lost for DDL of alter table .. add column ... *1. mysqld's error.log* 110803 3:39:16 InnoDB: Warning: problems renaming 'feel_22/#sql-2635_23d3a8' to 'feel_22/feed_send_1451', 25000 iterations （first 25000，fil0fil.c:: fil_rename_tablespace） InnoDB: Warning: tablespace './feel_22/#sql-2635_23d3a8.ibd' has i/o ops stopped for a long time 24999 （fil0fil.c:: fil_mutex_enter_and_prepare_for_io） 110803 3:39:16 InnoDB: Warning: problems renaming 'feel_22/#sql-2635_23d3a8' to 'feel_22/feed_send_1451', 25001 iterations （over 25000, return FALSE） 110803 3:39:16 [ERROR] Cannot find or open table feel_22/feed_send_1451 from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. there is another interesting error info: Error 1005: Can't create table 'feel_01.#sql-57f0_25a510' (errno: -1) *2. rename tablespace can be successful only if:* if (node-n_pending 0 || node-n_pending_flushes 0) if (node-modification_counter node-flush_counter) *3. we failed to repeat this bug and failed to locate the real reason. * Here is the information we got: * it's single table space with innodb plugin 1.0.9 and mysql-5.1.48. we failed to repeat this issue. * DDL is done at mid-night, and workload is very very slow(both master and slave suffered with issue but with very very low probability). * for 100G ibd file, fsync is so quickly that retry number is 0 for rename condition waiting, so we don't doult the n_pending_flushes. * all the sql are blocked when 2 retry first hit, but unfornantely no other stack/core info saved. * we suspect the io handlers are out-of-order,io_handler_threads and srv_master_thread maybe all os_event_wait_low. We can not prove the deadlock situation, but if the deadlock is exist in such situation, the patch maybe help us to suffering occasional table losting for DDL --- /tmp/mysql-5.1.48/storage/innodb_plugin/fil/fil0fil.c 2010-06-03 23:50:08.0 +0800 +++ storage/innodb_plugin/fil/fil0fil.c 2011-08-11 00:23:31.0 +++ +0800 @@ -938,8 +938,24 @@ mutex_exit(fil_system-mutex); + +#ifndef UNIV_HOTBACKUP +/* Wake the i/o-handler threads to make sure pending i/o's are + performed */ +os_aio_simulated_wake_handler_threads(); + os_thread_sleep(2); + /* Flush tablespaces so that we can close modified files in the LRU + list */ + +fil_flush_file_spaces(FIL_TABLESPACE); +#else + + os_thread_sleep(2); +#endif + + count2++; goto retry; @@ -2457,6 +2473,11 @@ fputs( to , stderr); ut_print_filename(stderr, new_name); fprintf(stderr, , %lu iterations\n, (ulong) count); + if (node) + fprintf(stderr, node info: n_pending=%lu, n_pending_flushes=%lu +modification_counter=%lu, flush_counter=%lu\n, +node-n_pending, node-n_pending_flushes, node-modification_counter, +node-flush_counter); } mutex_enter(fil_system-mutex); *4. we need yours help to solve the table lost issue*
can i replicating innodb table?
can i replicating innoble tables? does the master db and the slave db will having the same of information when they are doing replication? thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql on raid 1 or raid 5?
hi all, currently, i have a machine with raid 1 and raid 5 (backplane). in order to boost up the mysql performance, does it advise install /var/ (mysql data directory) into raid 1 or raid 5? please advise. thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: default table type = innodb is stable??
Is that stable if i started mysql server by defining default_table_type = INNODB at the my.cnf file? from which by default my.cnf is defining MYISAM table to be the defaulted. Richard Dale wrote: this is my error log file. InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 268435456 bytes! Your problem here is that you must have started MySQL when you had a 5MB transaction log file specified, but you then put a new config file online with a different log file size (256MB), InnoDB complains and dies. You need to delete your old transaction log files (ib_logfile0) then start MySQL and all should be fine. Note: You should only delete your log files when you are absolutely sure MySQL has shut down OK. Best regards, Richard Dale. Norgate Investor Services - Premium quality Stock, Futures and Foreign Exchange Data for markets in Australia, Asia, Canada, Europe, UK USA - www.premiumdata.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql connectivity error
hi all, i have a mysql which only localhost can be logged in. if i have created an account [EMAIL PROTECTED], then, i cant login in as that host. mysql -u user -h mymachine.com -p ERROR 2003 (HY000) Cant connect to the MySQL server on 'x.x.x.x' (111) please advise. thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: default table type = innodb is stable??
Jigal van Hemert wrote: - Original Message - From: Hiu Yen Onn [EMAIL PROTECTED] if i uncomment it, then mysql server wont start at all. if i comment it, then, that's ok. please advise. thanks again If the mysql server does not start it will probably leave a lot of messages in the error log. If you send the section of the error log about such a failed start to the list people here can most likely help you find the problem with your server. Regards, Jigal. this is my error log file. A mysqld process already exists at Sun Oct 16 09:33:39 BNT 2005 051016 9:36:14 [Note] /usr/sbin/mysqld: Normal shutdown 051016 9:36:14 InnoDB: Starting shutdown... 051016 9:36:17 InnoDB: Shutdown completed; log sequence number 0 43977 051016 9:36:17 [Note] /usr/sbin/mysqld: Shutdown complete 051016 09:36:17 mysqld ended 051016 09:36:17 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 268435456 bytes! 051016 9:36:18 [ERROR] Can't init databases 051016 9:36:18 [ERROR] Aborting 051016 9:36:18 [Note] /usr/sbin/mysqld: Shutdown complete 051016 09:36:18 mysqld ended 051016 09:37:41 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 268435456 bytes! 051016 9:37:41 [ERROR] Can't init databases 051016 9:37:41 [ERROR] Aborting 051016 9:37:41 [Note] /usr/sbin/mysqld: Shutdown complete 051016 09:37:41 mysqld ended 051016 09:39:02 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 268435456 bytes! 051016 9:39:03 [ERROR] Can't init databases 051016 9:39:03 [ERROR] Aborting 051016 9:39:03 [Note] /usr/sbin/mysqld: Shutdown complete 051016 09:39:03 mysqld ended -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
default table type = innodb is stable??
hi, i have a machine with 6G memory, loaded with RHEL4. now, my question is mysql support innodb as the default table type? will be stable running RHEL4? i saw /usr/share/mysql/my-innodb-heavy-4G.cnf file, then, i replace the existing one (/etc/my.cnf). but, it failed to start the mysql server. please advise. thanks? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: default table type = innodb is stable??
Are you using the my-innodb-heavy-4G.cnf file for your machine? i loaded the cnf file to /etc/my.cnf. then, it fails to start. what's wrong with it? mind to tell me on how to set the default table type equal to innodb?perhaps, can you guide me for cnf configuration for a 6G memory big machine for mysql? thanks again Ady Wicaksono wrote: Currently i have 4 Gbyte RAM and RH 9 Linux using InnoDB and yes, it's stable :) Hiu Yen Onn wrote: hi, i have a machine with 6G memory, loaded with RHEL4. now, my question is mysql support innodb as the default table type? will be stable running RHEL4? i saw /usr/share/mysql/my-innodb-heavy-4G.cnf file, then, i replace the existing one (/etc/my.cnf). but, it failed to start the mysql server. please advise. thanks? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: default table type = innodb is stable??
hereby, i attached the my.cnf file. by default, i copied it from /usr/share/mysql/my-huge.cnf. however, i have added default table type = INNODB. from the my.cnf, i can see that there are flags for innodb table, starting from # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = /var/lib/mysql/ #innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend #innodb_log_group_home_dir = /var/lib/mysql/ #innodb_log_arch_dir = /var/lib/mysql/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #innodb_buffer_pool_size = 384M #innodb_additional_mem_pool_size = 20M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 100M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 if i uncomment it, then mysql server wont start at all. if i comment it, then, that's ok. please advise. thanks again Hiu Yen Onn wrote: Are you using the my-innodb-heavy-4G.cnf file for your machine? i loaded the cnf file to /etc/my.cnf. then, it fails to start. what's wrong with it? mind to tell me on how to set the default table type equal to innodb?perhaps, can you guide me for cnf configuration for a 6G memory big machine for mysql? thanks again Ady Wicaksono wrote: Currently i have 4 Gbyte RAM and RH 9 Linux using InnoDB and yes, it's stable :) Hiu Yen Onn wrote: hi, i have a machine with 6G memory, loaded with RHEL4. now, my question is mysql support innodb as the default table type? will be stable running RHEL4? i saw /usr/share/mysql/my-innodb-heavy-4G.cnf file, then, i replace the existing one (/etc/my.cnf). but, it failed to start the mysql server. please advise. thanks? # Example MySQL config file for very large systems. # # This is for a large system with memory of 1G-2G where the system runs mainly # MySQL. # # You can copy this file to # /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is /var/lib/mysql) or # ~/.my.cnf to set user-specific options. # # In this file, you can use all long options that a program supports. # If you want to know which options a program supports, run the program # with the --help option. # The following options will be passed to all MySQL clients [client] #password = your_password port= 3306 socket = /var/lib/mysql/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] default-table-type = INNODB port= 3306 socket = /var/lib/mysql/mysql.sock skip-locking key_buffer = 384M max_allowed_packet = 1M table_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M read_rnd_buffer_size = 8M myisam_sort_buffer_size = 64M thread_cache = 8 query_cache_size = 32M # Try number of CPU's*2 for thread_concurrency thread_concurrency = 8 # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the enable-named-pipe option) will render mysqld useless! # #skip-networking # Replication Master Server (default) # binary logging is required for replication log-bin # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - #the syntax is: # #CHANGE MASTER TO MASTER_HOST=host, MASTER_PORT=port, #MASTER_USER=user, MASTER_PASSWORD=password ; # #where you replace host, user, password by quoted strings and #port by the master's port number (3306 by default). # #Example: # #CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, #MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then #start replication for the first time (even unsuccessfully, for example #if you mistyped the password in master-password and the slave fails to #connect), the slave will create a master.info file, and any later #change in this file to the variables' values below will be ignored and #overridden by the content of the master.info file, unless you shutdown #the slave server, delete master.info and restart the slaver server. #For that reason, you may want to leave the lines below untouched #(commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id
Newbie: MySQL cluster configuration
hi, i want to configure a two-machines mysql clusters. i have compiled from source by enabling the clustering feature with no problem at all. i read the documentation on mysql. but, i am not understanding on how to make a simple mysql cluster. basically, i just want to have a kickstart. that's all. i have a config.ini file at my /usr/local/mysql/mysql-cluster, as such [NDBD DEFAULT] NoOfReplicas= 1 [MYSQLD DEFAULT] [NDB_MGMD DEFAULT] [TCP DEFAULT] [NDB_MGMD] HostName= node1.mysql [NDBD] HostName= myhost.example.com DataDir= /var/lib/mysql-cluster [MYSQLD] [MYSQLD] [MYSQLD] then, when i start ndb_mgm, i get this. NDB SHOW Cluster Configuration - [ndbd(NDB)] 1 node(s) id=2@127.0.0.1 (Version: 3.5.3, Nodegroup: 0, Master) [ndb_mgmd(MGM)] 1 node(s) id=1@127.0.0.1 (Version: 3.5.3) [mysqld(API)] 3 node(s) id=3@127.0.0.1 (Version: 3.5.3) id=4 (not connected, accepting connect from any host) id=5 (not connected, accepting connect from any host) now, i have my second machine, let's called it node2.mysql. i have no ideas to join the ndb node2.mysql into the mgmd at node1.mysql. pls guide me. i read someone had mentionedNdb.cfg file. i have not noticed that file in my machine. weird pls give me more information and ideas.thanks -- Mr. Hiu Yen Onn System Administrator Shin Yang Group of companies Website: www.shinyang.com.my Email: [EMAIL PROTECTED] Tel: (6085)656699 ext.253 -- Butterfly de Micro$oft - The King of Desktops Penguin de Linux - The Mighty Lord of Servers -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
where is my my.cnf files??
hi, i compiled mysql-4.1.7 from source. actually, i want to configure a mysql cluster. from the documentation, i need to add some flag into a file called my.cnf. i searched through the files. it consisted of my-small.cnf, my-medium.cnf, my-huge.cnf. but, i cant see the file my.cnf file. where does it located pls enlighten me..thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql cluster installation
Hiu Yen Onn wrote: hi, I wish to have clusters of MySQL. i installed it from RPM. version, 4.1.7. but, i cant get the ndbd command to start my NDB. do i really need to install from tarball?? i am really new to MySQL clustering. all this while, i am using MySQL standalone database. pls guide me... i am willing to learn..thanks. how should i install the ndb cluster from source?? i read the article. it says BUILD/compile-pentium-max. but, then, from my tarball downloaded from mysql. it doesnt contain of such file. where should i get the proper source to build my ndb clusters? thanks pls enlighten me. thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql cluster installation
hi, I wish to have clusters of MySQL. i installed it from RPM. version, 4.1.7. but, i cant get the ndbd command to start my NDB. do i really need to install from tarball?? i am really new to MySQL clustering. all this while, i am using MySQL standalone database. pls guide me... i am willing to learn..thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
archive data
hi, i am using linux redhat 8 to power mysql. i installed mysql version 4.0.13 using rpm package. by default, the data file of mysql is alocated at /var/lib/mysql, but i have a limited of diskspace of /var dir (it is about 1G), so, it was easily full loaded with data. now, i want to archive the data into another dir. how can i switch the dir such that, i can have a spacious diskspace to store my data. now, i am facing a problem that i cant write into the db because of the no diskspace left. how can i archive my data, then, switch the storing location to another dir (previously it was /var/lib/mysql) which has bigger diskspace. then, restore the data. how can i do this? pls, advise. thanks Cheers, yenonn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Access my mysql db remotely...
i want to create a user who access from internet remotely to my db (outside firewall)? what is the solution then? how can i define the user accoutn? [EMAIL PROTECTED] Cheers, yenonn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
