rs now that I have upgraded to 5.0.38.
>> >> One question for people for whom expire_logs_days DOES work: do you
>> >> have any slaves connected to the server?
>> >>
>> >
>> > I did not within my test. I could easily add that if need be
however..
>&
o 5.0.38.
>> >> One question for people for whom expire_logs_days DOES work: do you
>> >> have any slaves connected to the server?
>> >>
>> >
>> > I did not within my test. I could easily add that if need be
however..
>> > Let me know if
Baron Schwartz wrote:
I think we've found the bug. I just did a bunch of tests and I'm 99%
sure not only does expire_logs_days not work if there are slaves
attached, neither does PURGE MASTER LOGS. When I read my email this
morning, Nagios alerted me the master server was over th
Hi,
Jake Peavy wrote:
On 5/4/07, Baron Schwartz <[EMAIL PROTECTED]> wrote:
Mark Leith wrote:
> Baron Schwartz wrote:
>> I will test again on my servers now that I have upgraded to 5.0.38.
>> One question for people for whom expire_logs_days DOES work: do you
>> h
-- Forwarded message --
From: Jake Peavy <[EMAIL PROTECTED]>
Date: May 4, 2007 7:41 AM
Subject: Re: expire_logs_days
To: Baron Schwartz <[EMAIL PROTECTED]>
On 5/4/07, Baron Schwartz <[EMAIL PROTECTED]> wrote:
Mark Leith wrote:
> Baron Schwartz wrote:
>&
Mark Leith wrote:
Baron Schwartz wrote:
I will test again on my servers now that I have upgraded to 5.0.38.
One question for people for whom expire_logs_days DOES work: do you
have any slaves connected to the server?
I did not within my test. I could easily add that if need be however
Baron Schwartz wrote:
I will test again on my servers now that I have upgraded to 5.0.38.
One question for people for whom expire_logs_days DOES work: do you
have any slaves connected to the server?
I did not within my test. I could easily add that if need be however..
Let me know if your
rking on roll; I
have no idea about restart.
I have a 4.1.13 server that's been up for 100 days. It has
expire_logs_days,
and I have 7 binlog files. I do flush my logs once a day to force the logs
to rotate.
So that's one confirmation that it works, at least in 4.1.13. :-)
This s
I have a 4.1.13 server that's been up for 100 days. It has
expire_logs_days,
and I have 7 binlog files. I do flush my logs once a day to force the
logs
to rotate.
So that's one confirmation that it works, at least in 4.1.13. :-)
This seems to work just fine on 5.0.40 as well:
medus
er that's been up for 100 days. It has
expire_logs_days,
and I have 7 binlog files. I do flush my logs once a day to force the
logs
to rotate.
So that's one confirmation that it works, at least in 4.1.13. :-)
This seems to work just fine on 5.0.40 as well:
medusa:/usr/local/mysql/
At 8:46 PM -0400 5/2/07, Baron Schwartz wrote:
Ofer Inbar wrote:
Mark Leith <[EMAIL PROTECTED]> wrote:
Do keep in mind that expire_logs_days only gets triggered at a)
server start up b) the time a binary log has to roll over.
If your binary logs do not roll over for quite a period o
Ofer Inbar wrote:
Mark Leith <[EMAIL PROTECTED]> wrote:
Do keep in mind that expire_logs_days only gets triggered at a) server
start up b) the time a binary log has to roll over.
If your binary logs do not roll over for quite a period of time (i.e are
lower load systems) that still s
Mark Leith <[EMAIL PROTECTED]> wrote:
> Do keep in mind that expire_logs_days only gets triggered at a) server
> start up b) the time a binary log has to roll over.
>
> If your binary logs do not roll over for quite a period of time (i.e are
> lower load systems) that s
er one to test now is test that this also happens when a
binary log rolls over.
Do keep in mind that expire_logs_days only gets triggered at a) server
start up b) the time a binary log has to roll over.
If your binary logs do not roll over for quite a period of time (i.e are
lower load system
Juan Eduardo Moreno wrote:
Hi,
I'm experience using expire_log_days and don't work. I set this
parameters
in the CNF and when the time of ( for example 5 days) is in, don't delete
anything.
On my expirience, this parameters don't work ( 5.0.27).
I am testing this now (on 5.0.40) and will se
it?
In what way did it not work?
The logs stayed in the directory. They did not get purged.
Tim Lucia <[EMAIL PROTECTED]> wrote:
We do the same thing, based on the "rumors" I read at the time I set it up.
(Where "rumors" means that googling for expire_logs_days revea
tried it?
In what way did it not work?
Tim Lucia <[EMAIL PROTECTED]> wrote:
> We do the same thing, based on the "rumors" I read at the time I set it
up.
> (Where "rumors" means that googling for expire_logs_days reveals many
with
> problems and not much good news.)
Has
way did it not work?
Tim Lucia <[EMAIL PROTECTED]> wrote:
> We do the same thing, based on the "rumors" I read at the time I set it up.
> (Where "rumors" means that googling for expire_logs_days reveals many with
> problems and not much good news.)
Has anyone her
> -Original Message-
> From: Baron Schwartz [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 02, 2007 7:55 AM
> To: Ofer Inbar
> Cc: mysql@lists.mysql.com
> Subject: Re: expire_logs_days
>
> Hi,
>
> Ofer Inbar wrote:
> > There's a system variable
Hi,
Ofer Inbar wrote:
There's a system variable called expire_logs_days that lets you set a
number of days to keep binary logs, and automatically delete logs
older than that. I've heard rumors that using this feature is
problematic. I notice that in the MySQL documentation ab
There's a system variable called expire_logs_days that lets you set a
number of days to keep binary logs, and automatically delete logs
older than that. I've heard rumors that using this feature is
problematic. I notice that in the MySQL documentation about binary
logging, it tells
ner [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, October 18, 2006 3:28 PM
>To: George Law
>Cc: mysql@lists.mysql.com
>Subject: Re: bin-log with expire_logs_days
>
>I haven't used the server variable you refer to, but instead have
>always used an external command piped in vi
ROTECTED]>;
Sent: Thursday, October 19, 2006 4:00 PM
Subject: Re: bin-log with expire_logs_days
Hi,
The system variable expire_logs_days removes the binary logs
automatically after the given number of days. The default is 0, which
means "no automatic removal." Possible removal
Hi,
The system variable expire_logs_days removes the binary logs automatically
after the given number of days. The default is 0, which means "no automatic
removal." Possible removals happen at startup and at binary log rotation.
For transactions, it never causes rotation instead
have 132 bin-logs, each at 1 GB. the logs go back to
2/11/2006
If I were to add 'expire_logs_days 45' to my.cnf and restart mysql, is
mysql going to attempt to purge the logs
> 45 days old and if so... how long does it typically take. We cannot
afford to restart if its going to ta
ql |grep bin
binlog_cache_size 32768
log_bin ON
max_binlog_cache_size 4294967295
max_binlog_size 1073741824
# echo "show status" | sql |grep bin
Com_show_binlog_events 0
Com_show_binlogs9
Right now, I have 132 bin-logs, each at 1 GB. the logs go back to
2/11/2006
I
26 matches
Mail list logo
