[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Q: Multiple accesslog overlays?
- To: Quanah Gibson-Mount <quanah@symas.com>
- Subject: Re: Q: Multiple accesslog overlays?
- From: Geert Hendrickx <geert@hendrickx.be>
- Date: Thu, 22 Aug 2019 20:09:59 +0200
- Cc: openldap-technical@openldap.org
- Content-disposition: inline
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=hendrickx.be; s=geert; t=1566497400; bh=j2Zzty8quJtdsPOFKy5SBcIPy1M0HT1c3ILoUpegEnQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Ye/m0otCWjCi1yaEQR8bla+Xurjke33Iye47qd2pc5kkm8pMNnt49EFmVkN+IncPD NCbTenOJMcncSavTNQt5LPD6LJY/gqbAzYG6Ul4r0P+YEyFIIwGwo8VLD8g1Ib3j7H aKrpybStuZsLen9jKHS9tGAfEdG6GAaZwz17tZdhTUe5lDCHd3RLE62EXltpVsHac9 VMxLAENLIKZK9YuiO1BZSCPG5zxiuAxemZ3KYnbkWxKjokadS+liWfaCOw4+v/nQMu 1ovVydQS2Z9TBrZfqSpHlAV/iMDzuO47SC434FRN/lQvO7B7NP8TJVC6tui4iLefZF CCO5XBONpfT1g==
- In-reply-to: <37AEDAE45AADCABE990E2FDD@[192.168.1.144]>
- References: <5D5A7817020000A100032F44@gwsmtp.uni-regensburg.de> <583C7259A5DA47BB10B2882B@[192.168.1.144]> <20190822111900.GA6110@vera.ghen.be> <95EB261DE85D6BE632FD93FB@[192.168.1.144]> <20190822133721.GA6841@vera.ghen.be> <37AEDAE45AADCABE990E2FDD@[192.168.1.144]>
- User-agent: Mutt/1.12.1 (2019-06-15)
On Thu, Aug 22, 2019 at 08:07:53 -0700, Quanah Gibson-Mount wrote:
> As you noted, overlays can intercept write operations. The problem is when
> an overlay intercepts a write op, where the write op occurs in the primary
> DB, but returns before accesslog is called, meaning that accesslog does not
> record the write op. This then breaks consistency between the servers.
> Since you're logging failures, you hit a different case, which generally
> underscores why this entire processing stack needs rewriting for 2.5.
Can that really happen between unique and accesslog overlays? The unique
overlay doesn't write any data itself, it will only reject certain writes?
The actual write to the underlying mdb database will only occur after it
passed through the entire overlay chain, or am I misunderstanding how it
works?
Geert
--
geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!