|
Re: [Bacula-users] Purge Log table - was: Re: Restore performance
2011-09-22 03:43:08
Le 22/09/2011 09:11, Eric Bollengier a écrit :
Hello,
Great information Chris , thank you!
However Marcio setup seems to show that the Log table is not purged as
expected.
I have checked on my setup too and while I have almost 2000 rows in y
Log table, I have only 150 entries in the Job table.
Having 10 lines of log per job is not unusual... (each row contains one
line of log).
that said, it seem more logical.
I double check using the following sql query and found sensible
value:
select JobId,count(*) from Log group by JobId;
...
152 rows in set (0.04 sec)
Having 150G for 2000 lines of log *is* unusual. It should be 200kB.
It's not me who have 150GB of Log table. I was just wondering why I
had 10 times more rows in log table than in job table.
I have my answer now. Thanks.
select count(*) from Log;
+----------+
| count(*) |
+----------+
| 1886 |
+----------+
select count(*) from Job;
+----------+
| count(*) |
+----------+
| 151 |
+----------+
Which tends to proove Log table is not pruned with associated Jobs.
Is it a bug?
It doesn't prove anything, except that something is uncorrectly
configured on the MySQL or on the system part.
Bye
--
Alexandre Chapellon
Ingénierie des systèmes open sources et
réseaux.
Follow me on twitter: @alxgomz
|
a_chapellon.vcf
Description: Vcard
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|
