Le 01/10/2015 19:50, Parrish, Kyle a écrit :
Well there was a small improvement. The total sync time is down to
about 40 minutes. Still too long though…
I have an idea, let me know if you think it will work.
I can add a new column to the SQL table stating weather the entry
needs to be “updated”, “added” or “removed.”
How can I configure LSC to just check these entries that have one of
these tags and update accordingly?
This would solve my time issue since we wouldn’t have any more than
about 10 changes per day. Eliminating the need to query 100,000
entries each cycle.
Hi Kyle,
it can be a solution. Add a column "state" with a value of "sync" for
all entries that mut be create or update. You can then adapt the SQL
query to only select entries for "sync" (with a simple WHERE clause) in
the LSC sync phase. But you need to find a way to update this column
after the LSC process, because LSC will not modify it (the source is
always read-only).
Fot the clean phase, I don't see how to proceed. As you know, LSC will
query the destination and for all entries found in the destination, it
will request the source to see if the entry is present. If not, the
entry is removed from the destination. So I don't see here how to use
the column "state".
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
