On 09/30/2016 02:15 AM, Noriko Hosoi wrote:
On 09/29/2016 05:43 AM, Ludwig Krispenz wrote:
> This is the initial proposal, thanks for your feedback
Please help me understanding the design...
I'm having a bit hard time to figure out the relationship/dependency
among these 3 config parameters.
sorry if I was not clear enough, I will update the doc, but let me try
to explain here
Are they independent or dependent? Do they take any combinations -- 2
* 3 * 2 == 12.
no. the primary parameter is: nsslapd-replica-accept-updates-state
If it is off, the other determine when it should be set to on again
(without an explicite change by an admin).
if it is on, the other two will not be used
independent of auto on/off the "delay" defines if(>=0) the state will be
reset to on and when
the "auto" param determines if the server should in the defined
it should try to detect if it is in sync and switch to "on" earlier.
There are 12 different behaviors? (assuming n for -delay is one case
What is your recommendation to the customers? I mean, what is the
that is a good question, there is the option to choose the default by
what is "my" recommendation (auto: on, delay: n) or what is backward
compatible (no change in default behaviour: auto off, delay: 0)
For instance, if -auto is "on", when an online init is executed on
the master, the scenario is automatically kicked in?
389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
To unsubscribe send an email to 389-devel-leave(a)lists.fedoraproject.org
Red Hat GmbH, http://www.de.redhat.com/
, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric