[rsyslog] Development of failsafe disk based queue

[Rainer Gerhards]

Hi RB,

I guess you've seen in the discussion (well, if you read all these
mails, I just noticed how many they were...) I am coming from the same
camp. But after all the dust settles, it looks like a very minor change
to rsyslog to allow the OS to do what it is expected to do. The queue
logic already cares about proper sequence (at least it should), the only
thing that is missing is to tell the OS to sync when we need it. The
spot to do so is also well defined, that is when the qi file is
persisted (because that completes the "queue transaction"). I will
verify with the code, but my current guess is that no more than 10 lines
of code will be needed to support this functionality. If so, I think it
is worth it.

More complex questions may arise (I have some on my mind) and that will
probably go beyond a general-purpose solution.

Rainer

On Wed, 2008-10-01 at 08:32 -0600, RB wrote:
> On Wed, Oct 1, 2008 at 06:57, Rainer Gerhards <rgerhards at hq.adiscon.com> wrote:
> > going back to the higher layer: do you say that immediate power failure
> > is a case that you consider needed to be addressed in an enterprise
> > logging system?
> >
> > Anybody else with an opinion?
> 
> Yes, I have an opinion: no.  Enterprise-grade applications need to
> make the best effort they can to be fault-tolerant and reliable, but
> we're following an exponential curve - at some point, you _have_ to
> give over to the hardware and OS engineers to do their job properly.
> Don't reinvent the hammer & chisel to reinvent the wheel - software
> can _never_ account for all hardware failures and should never be
> expected to do so.
> 
> 
> RB
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com