-
From: Brad Barnett [mailto:mysql-general-l...@l8r.net]
Sent: Friday, January 20, 2017 10:45 AM
To: mysql@lists.mysql.com
Subject: Re: io thread very slow copying binlogs
Hey Morgan,
Thanks for the tip. Might come in handy.
But, I'm positive it's not a disconnect / reconnect thing
200kbyte/sec / 1.6Mbit/sec right now.
It seems very steady too. As in, if I look at bytes, they're constantly
increasing.. just, slow..
On Fri, 20 Jan 2017 10:19:57 -0500
"Morgan Tocker" <morgan.toc...@oracle.com> wrote:
> Hi Brad,
>
> > MySQL community edition 5.6.29, run
t; On Fri, 20 Jan 2017 10:19:57 -0500
> > "Morgan Tocker" <morgan.toc...@oracle.com> wrote:
> >
> > > Hi Brad,
> > >
> > > > MySQL community edition 5.6.29, running Linux.
> > > >
> > > > Binlogs never seem to get ca
Hi Brad,
> MySQL community edition 5.6.29, running Linux.
>
> Binlogs never seem to get caught up on slaves.
>
> I've done all I can, to validate that this isn't network or disk related.
>
> Disk tests (using iostat and other methods) show lots of bandwidth left on
&
Hey all,
I have a weird issue.
MySQL community edition 5.6.29, running Linux.
Binlogs never seem to get caught up on slaves.
I've done all I can, to validate that this isn't network or disk related.
Disk tests (using iostat and other methods) show lots of bandwidth left
on the slave
/mysql. All works fine. Last week
I added this entry:
#expire bin logs
expire_logs_days = 7
to /usr/local/mysql/my.cnf
I restarted the MySQL server and now I have been waiting for the
binlogs to automatically expire but this is not happening:
$ ls -l /usr/local/mysql
-r--r--r
for the
binlogs to automatically expire but this is not happening:
$ ls -l /usr/local/mysql
-r--r--r-- 1 mysql mysql4954 Oct 1 07:30 my.cnf
drwx-- 2 mysql mysql1536 Sep 27 07:10 mysql
-rw-rw 1 mysql mysql 1073745213 Sep 2 04:07 mysql-bin.47
-rw-rw 1 mysql
Subject: mysql binlogs and their expiry times
Hi there,
I hope someone can help. Due to they way my HD has been sliced I had
to move mysql database to /usr/local/mysql. All works fine. Last week
I added this entry:
#expire bin logs
expire_logs_days = 7
to /usr/local/mysql/my.cnf
I restarted
Check show variables like 'expire_log%';
It must show expire_logs_days = 7
On Wed, Oct 8, 2008 at 2:44 PM, Zbigniew Szalbot [EMAIL PROTECTED] wrote:
Hello,
2008/10/8 Uma Bhat [EMAIL PROTECTED]:
To check the current my.cnf file which is being used by the server, use
below
$ ps -ef |
Hello,
2008/10/8 Uma Bhat [EMAIL PROTECTED]:
To check the current my.cnf file which is being used by the server, use
below
$ ps -ef | grep mysql
You should be able to see the my.cnf path used (usually specified in
--defaults-file=/path to my.cnf)
Yes, it was referring to the correct
2008/10/8 Rolando Edwards [EMAIL PROTECTED]:
At the Linux prompt, enter this : cat mysql-bin.index
Make sure every binlog is in the mysql-bin.index. If the list is incorrect,
then the expire logs feature won't work.
To test this out, try using PURGE MASTER LOGS TO ' mysql-bin.55';
If
have been waiting for the
binlogs to automatically expire but this is not happening:
$ ls -l /usr/local/mysql
-r--r--r-- 1 mysql mysql4954 Oct 1 07:30 my.cnf
drwx-- 2 mysql mysql1536 Sep 27 07:10 mysql
-rw-rw 1 mysql mysql 1073745213 Sep 2 04:07 mysql-bin
According to the doc for this parameter, Possible removals happen at
startup and at binary log rotation. This implies that removal is not
automatic - you have to either flush logs or bounce the server. We use
Purge Master periodically.
i do this from cron
mysql -e PURGE MASTER LOGS
we do the same thing. works just fine.
On Wed, Oct 8, 2008 at 10:55 AM, Tom Brown [EMAIL PROTECTED] wrote:
According to the doc for this parameter, Possible removals happen at
startup and at binary log rotation. This implies that removal is not
automatic - you have to either flush logs or
-
From: Jim Lyons [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2008 10:51 AM
To: Zbigniew Szalbot
Cc: mysql@lists.mysql.com
Subject: Re: mysql binlogs and their expiry times
According to the doc for this parameter, Possible removals happen at
startup and at binary log rotation
/local/mysql/my.cnf
I restarted the MySQL server and now I have been waiting for the
binlogs to automatically expire but this is not happening:
$ ls -l /usr/local/mysql
-r--r--r-- 1 mysql mysql4954 Oct 1 07:30 my.cnf
drwx-- 2 mysql mysql1536 Sep 27 07:10 mysql
-rw
Hello.
I've seen the 'PURGE MASTER LOGS TO 'mysql-bin.0XX';'
The complete syntax is available at:
http://dev.mysql.com/doc/refman/5.0/en/purge-master-logs.html
If you have replication you check that SLAVE has read binary logs
which you want to remove.
Luke Vanderfluit wrote:
Hi.
I have a production server that has a whole series of -bin files.
I want to get rid of them because they are consuming too much space.
Can I safely delete them?
Some date back to April of this year.
I've seen the 'PURGE MASTER LOGS TO 'mysql-bin.0XX';'
Thanks for any replies.
Kind
is replication
running and therefore old binlogs. These binlogs go back as far as Nov
12, 2004. The cleaning of the log table didn't start until about a
month ago and has deleted any data prior to Jan 18, 2005.
The only snapshot I can find of the database is from Sept 10, 2004.
So.. (shooting off
Dump the binarylogs into a text file greping all the log data in order
of oldest to newest (minus the massive delete). Then reply the events
backinto mysql
Mysqlbinlog binlogs in order |grep [your tablename] BIGSQLFILE.sql
mysql -uroot database BIGSQLFILE.sql
DVP
Dathan Vance
: Dathan Pattishall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 18, 2005 2:16 PM
To: Jeff McKeon; mysql@lists.mysql.com
Subject: RE: Restoring a database from binlogs
Dump the binarylogs into a text file greping all the log data
in order of oldest to newest (minus the massive delete
have however is replication
running and therefore old binlogs. These binlogs go back as far as Nov
12, 2004. The cleaning of the log table didn't start until about a
month ago and has deleted any data prior to Jan 18, 2005.
The only snapshot I can find of the database is from Sept 10, 2004
Mauro Marcellino [EMAIL PROTECTED] wrote:
Hello again...
I am transferring binlogs between two networks that are not connected as an offline
replication solution. I have two databases which I have configured the my.ini file
to create binlog entries for.
Do both databases get
Hello again...
I am transferring binlogs between two networks that are not connected as an offline
replication solution. I have two databases which I have configured the my.ini file to
create binlog entries for.
Do both databases get written to the same log or is there a separate log
On Thu, 2003-06-19 at 14:13, [EMAIL PROTECTED]
wrote:
binlog-do-db= test mysql
Hi,
There should only be one database per line:
binlog-do-db= test
binlog-do-db= mysql
regards,
Martin
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
Martin Waite writes:
On Thu, 2003-06-19 at 14:13, [EMAIL PROTECTED]
wrote:
binlog-do-db= test mysql
Hi,
There should only be one database per line:
binlog-do-db= test
binlog-do-db= mysql
How stupid of me not to have thought about this one
[EMAIL PROTECTED] wrote:
so there I am,
mysql server version 3.23.49-8.4
OS linux debian woody
box type i386
I've set up binlogs in my.cnf
I do get the binlog files created and rotated this with flush logs as
master reset.
I have the checkpoint and log_pos table set up.
what I do
Victoria Reznichenko writes:
[EMAIL PROTECTED] wrote:
so there I am,
mysql server version 3.23.49-8.4
OS linux debian woody
box type i386
I've set up binlogs in my.cnf
I do get the binlog files created and rotated this with flush logs as
master reset.
I have
Hi Folks,
so there I am,
mysql server version 3.23.49-8.4
OS linux debian woody
box type i386
I've set up binlogs in my.cnf
I do get the binlog files created and rotated this with flush logs as
master reset.
I have the checkpoint and log_pos table set up.
what I do not get is that the binlog
passwort?!? If it is, you may consider
changing it now. ;-)
I can see there is a -r function in mysqlimport, but of course the BinLogs
are in SQL format and this will not work
Any help would be GREATLY appreciated
p.s. suggesting that I use mysql's built in replication is not help.
Okay
--password=l4ka5Tdj databasename; done
I can see there is a -r function in mysqlimport, but of course the BinLogs
are in SQL format and this will not work
Any help would be GREATLY appreciated
p.s. suggesting that I use mysql's built in replication is not help.
Thanks,
Michael McConnell
Hi,
I've noticed, that bin logs names are followed by three digits: 001,002 and so
on. What will happen when I reach 999? Will it start to overwrite my first logs?
magic words: MySQL, table, sql
--
_/_/ _/_/_/ - Rafa Jank [EMAIL PROTECTED] -
_/ _/ _/ _/ _/
Rafal Jank writes:
Hi,
I've noticed, that bin logs names are followed by three digits: 001,002 and so
on. What will happen when I reach 999? Will it start to overwrite my first logs?
magic words: MySQL, table, sql
--
_/_/ _/_/_/ - Rafa³ Jank [EMAIL PROTECTED] -
I'm not the only one confused.
Any ideas?
Original Message
Subject: Re: Rotating the BINLogs
Date: 9 Feb 2001 12:37:03 -0300
From: "Rodolfo Sikora" [EMAIL PROTECTED]
To: Leonardo Dias [EMAIL PROTECTED]
I'm really confused like you.
I've been using flush logs on m
34 matches
Mail list logo
