Wednesday, May 31, 2017

[389-users] Re: enabled account policy plugin and incrace changelog db size


On 05/31/2017 01:44 AM, William Brown wrote:
On Tue, 2017-05-30 at 15:42 +0300, Alparslan Ozturk wrote:  
this is my person object and it has lastlogintime (the operational  attribute) so if many user bind the lastlogintime information updated so  replication is started. now I am changed agreement exclude lastlogintime  many replication is not accured. so changelogdb size slowly incrace. but  still incrace the size.      
  I don't think you can use fractionalReplication like this. Because you  end up commiting a change on either A or B master that can't be resolved  by the other, so the cl will grow forever.     Allow the replication of the attr :) 
the changes will be logged independent if they are replicated or not, so trimming is the only way to limit the size.
if you mean that trimming doesn't happen if the change is not rpelicated, this should be handled by the regular update of the "keep alive" entry, which will be replicated and update the consumer ruv, so that trimming can procede
    


_______________________________________________  389-users mailing list -- 389-users@lists.fedoraproject.org  To unsubscribe send an email to 389-users-leave@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 Shander

No comments:

Post a Comment