On Wed, 2018-08-15 at 11:03 -0600, Rich Megginson wrote:
> On 08/15/2018 10:56 AM, David Boreham wrote:
> >
> >
> > On 8/15/2018 10:36 AM, Rich Megginson wrote:
> > >
> > > Updating the csn generator and the uuid generator will cause a
> > > lot of
> > > churn in dse.ldif. There are other
On Tue, 2018-08-14 at 21:46 +, Devon Peters wrote:
> Hi folks,
>
> We've got multi-master replication setup between two masters. The
> replication recently broke after being stable for a few years, and in
> troubleshooting it appears that the issue is that both masters have
> the same
On Tue, 2018-08-14 at 10:36 -0600, David Boreham wrote:
>
> While it is true that you want to have the highest possible hit ratio
> on the two kinds of cache slapd maintains in order to achieve optimal
> read performance, you _can_ simply configure quite small caches for
> slapd (e.g. 1 few
On 08/15/2018 10:56 AM, David Boreham wrote:
On 8/15/2018 10:36 AM, Rich Megginson wrote:
Updating the csn generator and the uuid generator will cause a lot of
churn in dse.ldif. There are other housekeeping tasks which will
write dse.ldif
But if those things were being done so
On 8/15/2018 10:36 AM, Rich Megginson wrote:
Updating the csn generator and the uuid generator will cause a lot of
churn in dse.ldif. There are other housekeeping tasks which will
write dse.ldif
But if those things were being done so frequently that the resulting
filesystem I/O showed
On 08/15/2018 10:13 AM, David Boreham wrote:
in strace.log:
[pid 8088] 12:55:39.739539 poll([{fd=435, events=POLLOUT}], 1, 180
[pid 8058] 12:55:39.739573 <... write resumed> ) = 1 <0.87>
[pid 8088] 12:55:39.739723 <... poll resumed> ) = 1 ([{fd=435,
revents=POLLOUT}]) <0.000168>
in strace.log:
[pid 8088] 12:55:39.739539 poll([{fd=435, events=POLLOUT}], 1, 180
[pid 8058] 12:55:39.739573 <... write resumed> ) = 1 <0.87>
[pid 8088] 12:55:39.739723 <... poll resumed> ) = 1 ([{fd=435,
revents=POLLOUT}]) <0.000168>
[pid 8058] 12:55:39.739754 write(426, "dn:
Hi all, thanks for answering,
it took some time until I came again to this problem.
Am 09.08.2018 um 10:44 schrieb Ludwig Krispenz:
>
> On 08/09/2018 01:53 AM, William Brown wrote:
>> Sadly this doesn't tell us much :(
> we could get a pstack along with iotop to see which threads do teh IO,
