[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: n-way multi master and mirror mode
- To: Brendan Kearney <bpk678@gmail.com>
- Subject: Re: n-way multi master and mirror mode
- From: Quanah Gibson-Mount <quanah@symas.com>
- Date: Sun, 04 Dec 2016 10:22:15 -0800
- Cc: openldap-technical@openldap.org
- Content-disposition: inline
- In-reply-to: <WM!44ad0e380ee67a02e4d0d4461439cc67c76d8850ce4465b0ca5ddbc5fcadc3b8041b42450072f69bdcfa1c35f171a153!@mailstronghold-1.zmailcloud.com>
- References: <9d839f32-e456-045e-5372-b05b5510ba70@gmail.com> <WM!feac8b34acc61eba605a75d74631ee8ede6afaa7640ae0e8cd7125da3b0e1ab2629a6d8de581fa4d2d8ecd94372c70a1!@mailstronghold-1.zmailcloud.com> <4C4BC30AC646B3691A58116E@192.168.1.19> <CAARxGtj8b5bzkOtt8qQoCPh=Fyg5P+-JeVHvaEuRZyL==7+0jw@mail.gmail.com> <WM!12a8ed0e309de7b2311d33b30faaea8f0a7b1a603dad91c89f1716a98669134c72d098acb08ece8e9d7c8a9cb6f12f16!@mailstronghold-2.zmailcloud.com> <1B9342D9B4824860A82C5925@[192.168.1.19]> <b6790b82-f015-d3da-5300-e0e199be59a7@gmail.com> <WM!44ad0e380ee67a02e4d0d4461439cc67c76d8850ce4465b0ca5ddbc5fcadc3b8041b42450072f69bdcfa1c35f171a153!@mailstronghold-1.zmailcloud.com>
--On Saturday, December 03, 2016 6:42 PM -0500 Brendan Kearney
<bpk678@gmail.com> wrote:
where do i chase down the source of roughly 10k messages a week, given
that this is my home network? do i have a bottleneck in ldap? is
bind-dyndb-ldap pounding on ldap for some unknown reason? i dont believe
this to an appropriate amount of logs for what seems to be a low volume
network.
Hi Brendan,
a) This has nothing to do with MMR/Mirror Mode
b) It's not uncommon, and it rarely indicates a problem. Again, you would
need to show that things are actually being deferred for a significant
amount of time. Most often it is only for milliseconds. I.e., it's an
informational message that may or may not be indicative of a real issue.
Overall, you haven't really provided a lot of the necessary information to
help you move forward, such as:
OpenLDAP release
OpenLDAP backend(s) in use
Thread settings
concurrency settings
Specific messages of the problem
etc
For example, it could be the application(s) are poorly written, and fail to
use persistent connections, causing binds to be constantly be deferred. Or
it could be searches being deferred, etc. I.e., we have no idea /which/
operations are being deferred because you haven't provided that information.
I personally prefer applying the patch to OpenLDAP that provides timing
information for every operation so that I can actually tell whether or not
real problems are occurring. If that interests you, I can point you at it.
Hope that helps!
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>