Re: Slave is not updated
Hi Dilip, Thanks for your response I already run the below command at master: grant replication slave on *.* to 'mysqladm'@'95.84.86.41' identified by 'admmysql'; Thanks Jeetendra Ranjan - Original Message - From: Parikh, Dilip Kumar dilipkumar.par...@eds.com To: Jeetendra Ranjan jeetendra.ran...@sampatti.com; mysql@lists.mysql.com Sent: Thursday, December 24, 2009 1:10 PM Subject: RE: Slave is not updated You can see connecting to master means it is not able to establish the connection from slave to master, give the grants as (replication client etc..) and then try again. Thanks, Dilipkumar Database Engineering Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 1:05 PM To: mysql@lists.mysql.com Subject: Slave is not updated Hi, I am getting this information from slave mysql show slave status \G; *** 1. row *** Slave_IO_State: Connecting to master Master_Host: 201.107.236.77 Master_User: root Master_Port: 3306 Connect_Retry: 60 Master_Log_File: ip-201-107-236-77-bin.42 Read_Master_Log_Pos: 4702 Relay_Log_File: ip-95-84-86-41-relay-bin.01 Relay_Log_Pos: 98 Relay_Master_Log_File: ip-201-107-236-77-bin.42 Slave_IO_Running: No Slave_IO_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 4702 Relay_Log_Space: 98 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL The Slave_IO_Running is always No even after repeating below steps so many times stop slave CHANGE MASTER TO and start slave Please guide why this is always NO and how do i enable it ? Regards Jeetendra Ranjan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Slave is not updated
Jeetendra, Can you paste the error log here. -D -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 1:49 PM To: Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated Hi Dilip, Thanks for your response I already run the below command at master: grant replication slave on *.* to 'mysqladm'@'95.84.86.41' identified by 'admmysql'; Thanks Jeetendra Ranjan - Original Message - From: Parikh, Dilip Kumar dilipkumar.par...@eds.com To: Jeetendra Ranjan jeetendra.ran...@sampatti.com; mysql@lists.mysql.com Sent: Thursday, December 24, 2009 1:10 PM Subject: RE: Slave is not updated You can see connecting to master means it is not able to establish the connection from slave to master, give the grants as (replication client etc..) and then try again. Thanks, Dilipkumar Database Engineering Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 1:05 PM To: mysql@lists.mysql.com Subject: Slave is not updated Hi, I am getting this information from slave mysql show slave status \G; *** 1. row *** Slave_IO_State: Connecting to master Master_Host: 201.107.236.77 Master_User: root Master_Port: 3306 Connect_Retry: 60 Master_Log_File: ip-201-107-236-77-bin.42 Read_Master_Log_Pos: 4702 Relay_Log_File: ip-95-84-86-41-relay-bin.01 Relay_Log_Pos: 98 Relay_Master_Log_File: ip-201-107-236-77-bin.42 Slave_IO_Running: No Slave_IO_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 4702 Relay_Log_Space: 98 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL The Slave_IO_Running is always No even after repeating below steps so many times stop slave CHANGE MASTER TO and start slave Please guide why this is always NO and how do i enable it ? Regards Jeetendra Ranjan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=dhandapani.shanmu...@eds.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Slave is not updated
091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 6:58:30 InnoDB: Started; log sequence number 0 407843552 091223 6:58:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 6:58:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 98 091223 6:58:30 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:32 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:32 [Note] Slave I/O thread killed while connecting to master 091223 7:03:32 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:32 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:32 InnoDB: Starting shutdown... 091223 7:03:33 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 7:03:33 [Note] /usr/sbin/mysqld: Shutdown complete 091223 7:03:38 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:38 InnoDB: Started; log sequence number 0 407843552 091223 7:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:38 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.02' position: 98 091223 7:03:38 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:44 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:44 [Note] Slave I/O thread killed while connecting to master 091223 7:03:44 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:44 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:52 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:52 InnoDB: Started; log sequence number 0 407843552 091223 7:03:52 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:52 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.03' position: 98 091223 7:03:52 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:04:09 InnoDB: Error: table `horde/horde_sessionhandler` does not exist in the InnoDB internal InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Have you copied the .frm file of the table to the InnoDB: MySQL database directory from another database? InnoDB: You can look for further help from InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html 091223 7:30:52 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Lost connection to MySQL server at 'reading initial
RE: Slave is not updated
You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 6:58:30 InnoDB: Started; log sequence number 0 407843552 091223 6:58:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 6:58:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 98 091223 6:58:30 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:32 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:32 [Note] Slave I/O thread killed while connecting to master 091223 7:03:32 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:32 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:32 InnoDB: Starting shutdown... 091223 7:03:33 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 7:03:33 [Note] /usr/sbin/mysqld: Shutdown complete 091223 7:03:38 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:38 InnoDB: Started; log sequence number 0 407843552 091223 7:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:38 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.02' position: 98 091223 7:03:38 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:44 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:44 [Note] Slave I/O thread killed while connecting to master 091223 7:03:44 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:44 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:52 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:52 InnoDB: Started; log sequence number 0 407843552 091223 7:03:52 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:52 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.03' position: 98 091223 7:03:52 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using
RE: Slave is not updated
by the way did you flush the privileges on the master? What is the output you get, when you log in as root user on the mysql master server and issue the below command: select * from mysql.user where user='replication'\G; -D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:43 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 6:58:30 InnoDB: Started; log sequence number 0 407843552 091223 6:58:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 6:58:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 98 091223 6:58:30 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:32 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:32 [Note] Slave I/O thread killed while connecting to master 091223 7:03:32 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:32 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:32 InnoDB: Starting shutdown... 091223 7:03:33 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 7:03:33 [Note] /usr/sbin/mysqld: Shutdown complete 091223 7:03:38 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:38 InnoDB: Started; log sequence number 0 407843552 091223 7:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:38 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.02' position: 98 091223 7:03:38 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:44 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:44 [Note] Slave I/O thread killed while connecting to master 091223 7:03:44 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:44 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:52 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:52 InnoDB: Started; log sequence number 0 407843552 091223 7:03:52 [Note] /usr/sbin/mysqld: ready for connections. Version:
RE: Slave is not updated
User is not the replication it is 'root' (or) mysqladm Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Shanmugam, Dhandapani Sent: Thursday, December 24, 2009 2:48 PM To: Parikh, Dilip Kumar; Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated by the way did you flush the privileges on the master? What is the output you get, when you log in as root user on the mysql master server and issue the below command: select * from mysql.user where user='replication'\G; -D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:43 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 6:58:30 InnoDB: Started; log sequence number 0 407843552 091223 6:58:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 6:58:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 98 091223 6:58:30 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:32 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:32 [Note] Slave I/O thread killed while connecting to master 091223 7:03:32 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:32 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:32 InnoDB: Starting shutdown... 091223 7:03:33 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 7:03:33 [Note] /usr/sbin/mysqld: Shutdown complete 091223 7:03:38 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:38 InnoDB: Started; log sequence number 0 407843552 091223 7:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:38 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.02' position: 98 091223 7:03:38 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:44 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:44 [Note] Slave I/O thread killed while connecting to master 091223 7:03:44 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:44 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:52 [Warning] No argument was
RE: Slave is not updated
Jeetendra, just update the username as root on the below query select * from mysql.user where user='replication'\G; =D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:52 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated User is not the replication it is 'root' (or) mysqladm Thanks, Dilipkumar Database Engineering + mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Shanmugam, Dhandapani Sent: Thursday, December 24, 2009 2:48 PM To: Parikh, Dilip Kumar; Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated by the way did you flush the privileges on the master? What is the output you get, when you log in as root user on the mysql master server and issue the below command: select * from mysql.user where user='replication'\G; -D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:43 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 6:58:30 InnoDB: Started; log sequence number 0 407843552 091223 6:58:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 6:58:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 98 091223 6:58:30 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:32 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:32 [Note] Slave I/O thread killed while connecting to master 091223 7:03:32 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:32 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:32 InnoDB: Starting shutdown... 091223 7:03:33 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 7:03:33 [Note] /usr/sbin/mysqld: Shutdown complete 091223 7:03:38 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:38 InnoDB: Started; log sequence number 0 407843552 091223 7:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:38 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.02' position: 98 091223 7:03:38 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223
Re: Slave is not updated
Here is the action i performed: mysql GRANT REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'xx'@'xx.xx.xx.xx' IDENTIFIED BY ''; Query OK, 0 rows affected (0.00 sec) mysql Flush privileges; Query OK, 0 rows affected (0.00 sec) mysql select * from mysql.user where user='adconsent' \G; *** 1. row *** Host: xx.xx.xx.xx User: xxx Password: *02BF3AAD3EDAAD0A1C45A98092B24BDC96172E16 Select_priv: N Insert_priv: N Update_priv: N Delete_priv: N Create_priv: N Drop_priv: N Reload_priv: N Shutdown_priv: N Process_priv: N File_priv: N Grant_priv: N References_priv: N Index_priv: N Alter_priv: N Show_db_priv: N Super_priv: N Create_tmp_table_priv: N Lock_tables_priv: N Execute_priv: N Repl_slave_priv: Y Repl_client_priv: Y Create_view_priv: N Show_view_priv: N Create_routine_priv: N Alter_routine_priv: N Create_user_priv: N Event_priv: N Trigger_priv: N ssl_type: ssl_cipher: x509_issuer: x509_subject: max_questions: 0 max_updates: 0 max_connections: 0 max_user_connections: 0 1 row in set (0.00 sec) mysql show slave status \G; *** 1. row *** Slave_IO_State: Connecting to master Master_Host: xx.xx.xx.xx. Master_User: x Master_Port: 3306 Connect_Retry: 60 Master_Log_File: ip-xxx-xxx-xxx-xx-bin.42 Read_Master_Log_Pos: 7220 Relay_Log_File: ip-xx-xx-xx-xx-relay-bin.01 Relay_Log_Pos: 98 Relay_Master_Log_File: ip-xxx-xxx-xxx-xx-bin.42 Slave_IO_Running: No Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 7220 Relay_Log_Space: 98 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL Thanks Jeetendra Ranjan - Original Message - From: Shanmugam, Dhandapani dhandapani.shanmu...@eds.com To: Parikh, Dilip Kumar dilipkumar.par...@eds.com; Jeetendra Ranjan jeetendra.ran...@sampatti.com; mysql@lists.mysql.com Sent: Thursday, December 24, 2009 2:47 PM Subject: RE: Slave is not updated by the way did you flush the privileges on the master? What is the output you get, when you log in as root user on the mysql master server and issue the below command: select * from mysql.user where user='replication'\G; -D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:43 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as
Re: Slave is not updated
Please ignore the user name and ip. i am passing the right information here - Original Message - From: Parikh, Dilip Kumar dilipkumar.par...@eds.com To: Jeetendra Ranjan jeetendra.ran...@sampatti.com; mysql@lists.mysql.com Sent: Thursday, December 24, 2009 2:51 PM Subject: RE: Slave is not updated User is not the replication it is 'root' (or) mysqladm Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Shanmugam, Dhandapani Sent: Thursday, December 24, 2009 2:48 PM To: Parikh, Dilip Kumar; Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated by the way did you flush the privileges on the master? What is the output you get, when you log in as root user on the mysql master server and issue the below command: select * from mysql.user where user='replication'\G; -D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:43 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 6:55:45 [Note] /usr/sbin/mysqld: Shutdown complete 091223 6:58:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 6:58:30 InnoDB: Started; log sequence number 0 407843552 091223 6:58:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 6:58:30 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 98 091223 6:58:30 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:32 [Note] /usr/sbin/mysqld: Normal shutdown 091223 7:03:32 [Note] Slave I/O thread killed while connecting to master 091223 7:03:32 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 7:03:32 [Note] Error reading relay log event: slave SQL thread was killed 091223 7:03:32 InnoDB: Starting shutdown... 091223 7:03:33 InnoDB: Shutdown completed; log sequence number 0 407843552 091223 7:03:33 [Note] /usr/sbin/mysqld: Shutdown complete 091223 7:03:38 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ip-97-74-85-42-bin' to avoid this problem. 091223 7:03:38 InnoDB: Started; log sequence number 0 407843552 091223 7:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.85-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL) 091223 7:03:38 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.02' position: 98 091223 7:03:38 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 7:03:44 [Note] /usr/sbin/mysqld: Normal
Re: Slave is not updated
who is 'adconsent' ??. what is your replication user -naga On Thu, Dec 24, 2009 at 3:01 PM, Jeetendra Ranjan jeetendra.ran...@sampatti.com wrote: Here is the action i performed: mysql GRANT REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'xx'@'xx.xx.xx.xx' IDENTIFIED BY ''; Query OK, 0 rows affected (0.00 sec) mysql Flush privileges; Query OK, 0 rows affected (0.00 sec) mysql select * from mysql.user where user='adconsent' \G; *** 1. row *** Host: xx.xx.xx.xx User: xxx Password: *02BF3AAD3EDAAD0A1C45A98092B24BDC96172E16 Select_priv: N Insert_priv: N Update_priv: N Delete_priv: N Create_priv: N Drop_priv: N Reload_priv: N Shutdown_priv: N Process_priv: N File_priv: N Grant_priv: N References_priv: N Index_priv: N Alter_priv: N Show_db_priv: N Super_priv: N Create_tmp_table_priv: N Lock_tables_priv: N Execute_priv: N Repl_slave_priv: Y Repl_client_priv: Y Create_view_priv: N Show_view_priv: N Create_routine_priv: N Alter_routine_priv: N Create_user_priv: N Event_priv: N Trigger_priv: N ssl_type: ssl_cipher: x509_issuer: x509_subject: max_questions: 0 max_updates: 0 max_connections: 0 max_user_connections: 0 1 row in set (0.00 sec) mysql show slave status \G; *** 1. row *** Slave_IO_State: Connecting to master Master_Host: xx.xx.xx.xx. Master_User: x Master_Port: 3306 Connect_Retry: 60 Master_Log_File: ip-xxx-xxx-xxx-xx-bin.42 Read_Master_Log_Pos: 7220 Relay_Log_File: ip-xx-xx-xx-xx-relay-bin.01 Relay_Log_Pos: 98 Relay_Master_Log_File: ip-xxx-xxx-xxx-xx-bin.42 Slave_IO_Running: No Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 7220 Relay_Log_Space: 98 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL Thanks Jeetendra Ranjan - Original Message - From: Shanmugam, Dhandapani dhandapani.shanmu...@eds.com To: Parikh, Dilip Kumar dilipkumar.par...@eds.com; Jeetendra Ranjan jeetendra.ran...@sampatti.com; mysql@lists.mysql.com Sent: Thursday, December 24, 2009 2:47 PM Subject: RE: Slave is not updated by the way did you flush the privileges on the master? What is the output you get, when you log in as root user on the mysql master server and issue the below command: select * from mysql.user where user='replication'\G; -D -Original Message- From: Parikh, Dilip Kumar [mailto:dilipkumar.par...@eds.com] Sent: Thursday, December 24, 2009 2:43 PM To: Jeetendra Ranjan; mysql@lists.mysql.com Subject: RE: Slave is not updated You can see in the logs, access denied So give trying for hostname or with full domain or Grant replication slave on *.* to 'mysqladm'@'95.%' identified by 'xx'; Grant replication slave on *.* to 'mysqladm'@'hostname identified by 'xx'; Flush privileges; it should work. Thanks, Dilipkumar Database Engineering mailto: dilipkumar.par...@eds.com Pager mail:9884430...@nma.vodafone.in mail%3a9884430...@nma.vodafone.in -Original Message- From: Jeetendra Ranjan [mailto:jeetendra.ran...@sampatti.com] Sent: Thursday, December 24, 2009 2:31 PM To: Shanmugam, Dhandapani; Parikh, Dilip Kumar; mysql@lists.mysql.com Subject: Re: Slave is not updated 091223 5:55:22 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/var/lib/mysql/mysql-relay-bin.01' position: 4 091223 5:55:22 [ERROR] Slave I/O thread: error connecting to master 'r...@201.107.236.77:3306': Error: 'Access denied for user 'root'@'ip-97-74-85-42.ip.secureserver.net' (using password: YES)' errno: 1045 retry-time: 60 retries: 86400 091223 6:55:42 [Note] /usr/sbin/mysqld: Normal shutdown 091223 6:55:42 [Note] Slave I/O thread killed while connecting to master 091223 6:55:42 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4 091223 6:55:42 [Note] Error reading relay log event: slave SQL thread was killed 091223 6:55:42 InnoDB: Starting shutdown... 091223 6:55:45 InnoDB: Shutdown
Re: Table level locking when inserting auto-increment PK to InnoDB
2009/12/23 Ryan Chan ryanchan...@gmail.com: Hey. Back to few years ago, InnoDB require table level locking when inserting auto-increment PK to the table, and Heikki said there will be a fix. Is this problem still exist now? If you refer to this bug: http://bugs.mysql.com/bug.php?id=16979 there is a manual page discussing the changes done for the 5.1 version: http://dev.mysql.com/doc/refman/5.1/en/innodb-auto-increment-handling.html -- Jaime Crespo MySQL Java Instructor Warp Networks http://warp.es -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql load balancing
El día 22 de diciembre de 2009 13:44, Miguel Angel Nieto cor...@miguelangelnieto.net escribió: It depends a lot on how you plan to coordinate the db servers (sharding, replication, ndb), the kind of applications you are going to deploy and how much scability you need. Thank you. I have read about LVS and keepalived but I can't see the difference between them. Are they the same thing? I want the load balancing for my replicated servers. I suppose that LVS can't distinguish between inserts and selects (to send queries to the master o slave server). I do not know about keepalived, but it seems to provide the same service that heartbeat does: user-level awareness of the failure of a machine or a service. LVM, however, does kernel module, ip-level, load balancing and automatic failure clustering. The big confusion with those apps is that most of them are extensible and combinable to achieve the same goal. About the read/write balancing (which is a good question, and that is why I asked what you were intending to do on the other end), I have seen it done **only at application level**, not transparently, because of the problems derived from asynchronous replication (lag between master writes and slaves see the data). I am sorry I cannot help you, but please, share here if you found something useful AND with good performance. Merry Xmas! -- Jaime Crespo MySQL Java Instructor Warp Networks http://warp.es -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql load balancing
Hi, I've had quite a bit of success deploying mysql-proxy in my clients infrastructure. The standard read/write splitting is quite easy to achieve - but I also add some custom code to match with specific case (connection pooling, x second to the same master after a write/update, specific command goes to this specific 'async' server...). Since the 'rewrite' language is LUA its is quite easy to extend the feature. I did complete some benchmarks of those systems for a client (overhead cost) but I don't know if they are ready to share them (and I don't have access to them since I'm mobile right now). Ill inquire. P. On 12/24/09, Jaime Crespo Rincón jcre...@warp.es wrote: El día 22 de diciembre de 2009 13:44, Miguel Angel Nieto cor...@miguelangelnieto.net escribió: It depends a lot on how you plan to coordinate the db servers (sharding, replication, ndb), the kind of applications you are going to deploy and how much scability you need. Thank you. I have read about LVS and keepalived but I can't see the difference between them. Are they the same thing? I want the load balancing for my replicated servers. I suppose that LVS can't distinguish between inserts and selects (to send queries to the master o slave server). I do not know about keepalived, but it seems to provide the same service that heartbeat does: user-level awareness of the failure of a machine or a service. LVM, however, does kernel module, ip-level, load balancing and automatic failure clustering. The big confusion with those apps is that most of them are extensible and combinable to achieve the same goal. About the read/write balancing (which is a good question, and that is why I asked what you were intending to do on the other end), I have seen it done **only at application level**, not transparently, because of the problems derived from asynchronous replication (lag between master writes and slaves see the data). I am sorry I cannot help you, but please, share here if you found something useful AND with good performance. Merry Xmas! -- Jaime Crespo MySQL Java Instructor Warp Networks http://warp.es -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=pascal.char...@gmail.com -- Sent from my mobile device -- Pascal Charest, skype: pascal.charest Free software consultant @ Laboratoire Phoenix http://www.labsphoenix.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Best Solution /more Tables or all in one?/
Hi i am on to create a database with a lot of entries. each user may have Records like: data1 (textfield) data2 (textfield) data3 (char [300]) and more like that Now I am thinking about what is better a: to create for each field an own Table like: table_user_data1 (records: userid, data1) table_user_data2(records: userid, data2) table_user_data3(records: userid, data3) b: or to make one table with all included like: Table_userData records: (Userid, data1,data2,data3) My thinking is: When i make solution a) contra: i would have several Tabels to scan to get all data pro: there is only data saved in my database that is used when i do solution b) contra: when I only save in info in data1 and dont need more, it also save empty fields for data2 and data3 pro: I may only scan one table to get all my infos What do you think? I hope I did not explained to complicated :) Greets Chris
two processes update the same column in short time
Hello, I have a table, say its stru is like: domain ip noticed The column noticed is an enum value (eigher 0 or 1). When process one update ip, it will set noticed to 0. Then process two know the status changed, it will do something and set noticed to 1. What the problem I meet is, when process two read ip from the table, and before it update the noticed to 1 (it has to do something with the ip, and this will take few seconds), process one also updated the table with new ip and noticed=0. Under this case, process two has gotten the outdated IPs (not the new ones updated by process one), since it will set noticed=1 finally so it doesn't have a chance to find it's using old IPs. So how to resolve this problem? Thanks for my newbie questions. Merry Holidays! Eva.
