RE: /etc/init.d/mysql start WITHOUT integrity check?
Daevid, I'm not quite sure I understand why you want to restart your master. Adding a slave shouldn't require any restarts/reloads. What have you changed in the my.cnf to solicit a restart? Andy From: ext Daevid Vincent [dae...@daevid.com] Sent: 29 December 2010 20:25 To: 'mysql' Subject: /etc/init.d/mysql start WITHOUT integrity check? Is there a way to /etc/init.d/mysql start WITHOUT doing an integrity check? Can I pass in a command line parameter or set something in the my.cnf file? Our DB is a Billion rows (with a B) and that check can take HOURS. All we want to do is restart the server to put another slave online because sadly /etc/init.d/mysql reload does NOT re-load the config file (as one might hope), it is only to reload PRIVS (how useless is that since GRANT already does that). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=andrew.2.mo...@nokia.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: /etc/init.d/mysql start WITHOUT integrity check?
Let me know with you whether I understood what do you want to do. Normally, after mysqld restart on OSs as Ubuntu/Debian, we can observe a script execution, which will check integrity of all databases tables and present a message of Corrupt What I did when I wanted to get rid this check of was comment the lines inside the file script with # character. Please, let us know if it is the operation do you want to avoid when restart mysqld. Best regards. -- Wagner Bianchi 2010/12/30 andrew.2.mo...@nokia.com Daevid, I'm not quite sure I understand why you want to restart your master. Adding a slave shouldn't require any restarts/reloads. What have you changed in the my.cnf to solicit a restart? Andy From: ext Daevid Vincent [dae...@daevid.com] Sent: 29 December 2010 20:25 To: 'mysql' Subject: /etc/init.d/mysql start WITHOUT integrity check? Is there a way to /etc/init.d/mysql start WITHOUT doing an integrity check? Can I pass in a command line parameter or set something in the my.cnf file? Our DB is a Billion rows (with a B) and that check can take HOURS. All we want to do is restart the server to put another slave online because sadly /etc/init.d/mysql reload does NOT re-load the config file (as one might hope), it is only to reload PRIVS (how useless is that since GRANT already does that). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=andrew.2.mo...@nokia.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=wagnerbianch...@gmail.com
RE: /etc/init.d/mysql start WITHOUT integrity check?
-Original Message- From: andrew.2.mo...@nokia.com [mailto:andrew.2.mo...@nokia.com] Sent: Thursday, December 30, 2010 2:45 AM To: dae...@daevid.com; mysql@lists.mysql.com Subject: RE: /etc/init.d/mysql start WITHOUT integrity check? Daevid, I'm not quite sure I understand why you want to restart your master. Adding a slave shouldn't require any restarts/reloads. What have you changed in the my.cnf to solicit a restart? It requires a restart of the slave mysql server. It also requires shutting down the master so that no data is written while we copy the snapshot to the slave. http://dev.mysql.com/doc/refman/5.0/en/replication-howto-existingdata.html Andy From: ext Daevid Vincent [dae...@daevid.com] Sent: 29 December 2010 20:25 To: 'mysql' Subject: /etc/init.d/mysql start WITHOUT integrity check? Is there a way to /etc/init.d/mysql start WITHOUT doing an integrity check? Can I pass in a command line parameter or set something in the my.cnf file? Our DB is a Billion rows (with a B) and that check can take HOURS. All we want to do is restart the server to put another slave online because sadly /etc/init.d/mysql reload does NOT re-load the config file (as one might hope), it is only to reload PRIVS (how useless is that since GRANT already does that). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=andrew.2.mo...@nokia.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: /etc/init.d/mysql start WITHOUT integrity check?
Comment WHAT lines? I looked through /etc/init.d/mysql and don't see anything related to check or chk. I eyeballed each line in the file and nothing stands out as the culprit causing an integrity check of the databases. develo...@mypse:/etc/init.d$ ps aux | grep mysql 46:root 10239 0.0 0.1 1680 520 ?SDec25 0:00 /bin/sh /usr/bin/mysqld_safe 49:mysql11165 0.0 5.4 129924 27864 ?Sl Dec25 0:58 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock 50:root 11167 0.0 0.1 2920 692 ?SDec25 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld 81:1000 19149 0.0 0.1 3004 788 pts/0R+ 21:54 0:00 grep -n -i --color=auto mysql mailto:develo...@mypse:/etc/init.d$ develo...@mypse:/etc/init.d$ cat /proc/11165/cmdline /usr/sbin/mysqld--basedir=/usr--datadir=/var/lib/mysql--user=mysql--pid-fil e=/var/run/mysqld/mysqld.pid--skip-external-locking--port=3306--socket=/var /run/mysqld/mysqld.sockd Does anyone know if a kill -SIGHUP 11165 will cause a reload of the configuration? _ From: Wagner Bianchi [mailto:wagnerbianch...@gmail.com] Sent: Thursday, December 30, 2010 5:01 AM To: andrew.2.mo...@nokia.com Cc: dae...@daevid.com; mysql@lists.mysql.com Subject: Re: /etc/init.d/mysql start WITHOUT integrity check? Let me know with you whether I understood what do you want to do. Normally, after mysqld restart on OSs as Ubuntu/Debian, we can observe a script execution, which will check integrity of all databases tables and present a message of Corrupt What I did when I wanted to get rid this check of was comment the lines inside the file script with # character. Please, let us know if it is the operation do you want to avoid when restart mysqld. Best regards. -- Wagner Bianchi 2010/12/30 andrew.2.mo...@nokia.com Daevid, I'm not quite sure I understand why you want to restart your master. Adding a slave shouldn't require any restarts/reloads. What have you changed in the my.cnf to solicit a restart? Andy From: ext Daevid Vincent [dae...@daevid.com] Sent: 29 December 2010 20:25 To: 'mysql' Subject: /etc/init.d/mysql start WITHOUT integrity check? Is there a way to /etc/init.d/mysql start WITHOUT doing an integrity check? Can I pass in a command line parameter or set something in the my.cnf file? Our DB is a Billion rows (with a B) and that check can take HOURS. All we want to do is restart the server to put another slave online because sadly /etc/init.d/mysql reload does NOT re-load the config file (as one might hope), it is only to reload PRIVS (how useless is that since GRANT already does that). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=andrew.2.mo...@nokia.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=wagnerbianch...@gmail.com
Re: /etc/init.d/mysql start WITHOUT integrity check?
On 12/30/2010 5:00 PM, Daevid Vincent wrote: Comment WHAT lines? I looked through /etc/init.d/mysql and don't see anything related to check or chk. I eyeballed each line in the file and nothing stands out as the culprit causing an integrity check of the databases. develo...@mypse:/etc/init.d$ ps aux | grep mysql 46:root 10239 0.0 0.1 1680 520 ?SDec25 0:00 /bin/sh /usr/bin/mysqld_safe 49:mysql11165 0.0 5.4 129924 27864 ?Sl Dec25 0:58 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock 50:root 11167 0.0 0.1 2920 692 ?SDec25 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld 81:1000 19149 0.0 0.1 3004 788 pts/0R+ 21:54 0:00 grep -n -i --color=auto mysql mailto:develo...@mypse:/etc/init.d$ develo...@mypse:/etc/init.d$ cat /proc/11165/cmdline /usr/sbin/mysqld--basedir=/usr--datadir=/var/lib/mysql--user=mysql--pid-fil e=/var/run/mysqld/mysqld.pid--skip-external-locking--port=3306--socket=/var /run/mysqld/mysqld.sockd Does anyone know if a kill -SIGHUP 11165 will cause a reload of the configuration? It won't reload the configuration. http://dev.mysql.com/doc/refman/5.1/en/server-signal-response.html Are you sure you aren't seeing the results of a dirty shutdown and auto-recovery? -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: /etc/init.d/mysql start WITHOUT integrity check?
There are different and connected things being discussed here. 1-) Is there a way to read new configurations from my.cnf whithout restart server? = No. A simple mysqladmin reaload don't submit server to read configuration file again. 2-) Is there a way to avoid debian-script to check databases' integrity? = Yeah, there is! Open the debian script and comment all rows. Best regards. -- Wagner Bianchi 2010/12/30 Shawn Green shawn.l.gr...@oracle.com On 12/30/2010 5:00 PM, Daevid Vincent wrote: Comment WHAT lines? I looked through /etc/init.d/mysql and don't see anything related to check or chk. I eyeballed each line in the file and nothing stands out as the culprit causing an integrity check of the databases. develo...@mypse:/etc/init.d$ ps aux | grep mysql 46:root 10239 0.0 0.1 1680 520 ?SDec25 0:00 /bin/sh /usr/bin/mysqld_safe 49:mysql11165 0.0 5.4 129924 27864 ?Sl Dec25 0:58 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock 50:root 11167 0.0 0.1 2920 692 ?SDec25 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld 81:1000 19149 0.0 0.1 3004 788 pts/0R+ 21:54 0:00 grep -n -i --color=auto mysql mailto:develo...@mypse:/etc/init.d$ develo...@mypse:/etc/init.d$ cat /proc/11165/cmdline /usr/sbin/mysqld--basedir=/usr--datadir=/var/lib/mysql--user=mysql--pid-fil e=/var/run/mysqld/mysqld.pid--skip-external-locking--port=3306--socket=/var /run/mysqld/mysqld.sockd Does anyone know if a kill -SIGHUP 11165 will cause a reload of the configuration? It won't reload the configuration. http://dev.mysql.com/doc/refman/5.1/en/server-signal-response.html Are you sure you aren't seeing the results of a dirty shutdown and auto-recovery? -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=wagnerbianch...@gmail.com
