On 19.05.2016 09:30, Stanislav Laznicka wrote:
On 05/19/2016 08:52 AM, Ludwig Krispenz wrote:
On 05/19/2016 08:02 AM, Stanislav Laznicka wrote:
On 05/18/2016 04:44 PM, Petr Vobornik wrote:
On 05/18/2016 04:36 PM, Stanislav Laznicka wrote:
There's no ticket for this patch but as there was a fix to 389-ds
mentioned in https://fedorahosted.org/freeipa/ticket/5396, the TODO
section in clean_dangling_ruvs could be removed.
What about using
'replica-force-cleaning':'yes',
every time?
Is there a drawback which we would like to avoid?
The DS website mentions two possible risks
- possible loss of changes on deleted replica should these have not
been reflected to some other replicas
this is a theoretical concern that there might be changes from the
replica to be removed which are not yet on all servers, but to me the
problem that cleaning ruvs hangs because replicas cannot be reached
is the worse scenario.
- if some offline replica comes back online, it may re-pollute the
RUVs back
I'm not sure of the probability of the second scenario, in my rather
simple environment the re-pollution did not happen.
there have been fixes in 389-ds to prevent the repollution, so it
should no longer happen.
Thank you, Ludwig. It seems reasonable to have the option set to 'yes'
all the time, then.
ACK
Pushed to:
master: 0492ab9c0a014735f09e82d5db1c4c1aa2bd6d81
ipa-4-3: d7985af911d54d3ea2637cd8200aeff5d66638d5
--
Manage your subscription for the Freeipa-devel mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-devel
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code
