Hi, On Thu, Mar 20, 2014 at 5:50 AM, Alex Parvulescu <[email protected]> wrote: > Th problem I experienced comes in when there is enough content writes that > a segment flush is triggered, so basically the same node, even unchanged > ends up in a different segment, so with a different segment id.
Hmm, I believe you're seeing something different here, as a flush will never change the identifier of a node. > With time more and more segments are created, and as far as I can see nodes > that have no changes migrate to different segments. An unchanged node should never move from one segment to another within a given repository. Perhaps the comparison is between content in the source repository and that in the backup repository? In that case the segment identifiers wouldn't match, and the comparison would slow down as described. BR, Jukka Zitting
