[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] mysqlfs
- Subject: [ale] mysqlfs
- From: Richard at Bronosky.com (Richard Bronosky)
- Date: Mon, 17 May 2010 19:37:38 -0400
- In-reply-to: <1274135123.15747.6.camel@cfowler-desktop>
- References: <1274110407.2129.14.camel@cfowler-laptop> <[email protected]> <1274135123.15747.6.camel@cfowler-desktop>
I realize that syslog is not involved. I'm suggesting that it could
server your needs. Your concern about binlog size is only the tip of
the concern-berg. Unless there is something about MySQL that you need
for this purpose, I'd recommend against it. My first choice would be a
syslog server. My second would be RRDTool.
On 5/17/10, Chris Fowler <cfowler at outpostsentinel.com> wrote:
> On Mon, 2010-05-17 at 17:34 -0400, Richard Bronosky wrote:
>> Sounds like a remote syslog server. What part of your needs are missed
>> by syslog and met by mysql? (I'm speaking as a MySQL DBA.)
>
> No syslog involved. These are console logs coming off many devices.
> I've debated about modifying my program to store this data in MYSQL but
> am trying mysqlfs now. Performance is a non-issue for these. I'm also
> doing replication and my only concern is that with the possible high
> number of transactions the bin-logs could get very big very fast. Maybe
> I should create a cron job to clean them?
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
--
Sent from my mobile device
.!# RichardBronosky #!.
- Follow-Ups:
- [ale] mysqlfs
- From: cfowler at outpostsentinel.com (Chris Fowler)