[
https://issues.apache.org/jira/browse/DIRSERVER-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541888
]
Alex Karasulu commented on DIRSERVER-1097:
------------------------------------------
Great idea! I was thinking we can do similar optimizations as well when
dealing with reverting things in this ChangeLog thing we're working on now.
The idea is the same, if in rev 10 an entry is created, then modified in 200,
2345, and deleted in 94872. Then reverting to rev 7 for example would
essentially not include anything with respect to this entry. The code in the
replication subsystem and the changelog shapshotting would essentially have to
do similar things. Perhaps we can share this code.
I think there is intense synergy and complementation between this changelog
feature and the replication subsystem. I'm trying to grasp how revision
numbers can be used in concert with UUIDs to manage various tasks. Also
thinking about how the two can better compliment each other. I'd be interested
in any thoughts you may have on the matter.
> Only send net changes during replication
> ----------------------------------------
>
> Key: DIRSERVER-1097
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1097
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
> Priority: Minor
>
> During replication we currently send all changes that have occurred since the
> target replica was last brought up to date. We can optimise this by only
> sending the net changes. As an example, if an entry is created, modified
> several times then deleted at one server, we do not need to tell other
> replicas anything regarding this entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
