jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea K." <akre...@alteanet.it>
Subject Re: > Indexes Backup
Date Mon, 19 Nov 2007 10:02:58 GMT

So, regarding my starting example.
If I restore indexes to revision 120 on Server1, some future (self) revision
will be skipped?

In this case, there's no way (or reason) to backup indexes!

You can never return to a consistent index because some revisions will be
skipped by Server1, and consequently, some data will never be searcheable on
Server1. Is it right or I'm wrong?

Is it a correct behaviour also if the server restarts from an old revision?!

So, any idea to backup the system/indexes in a correct way?


Dominique Pfister wrote:
> On 19/11/2007, Marcel Reutegger <marcel.reutegger@gmx.net> wrote:
>> Andrea K. wrote:
>> > Hi Marcel,
>> > my question is exactly over this point.
>> >
>> > I know that it will not re-index all the repository. As I often see
>> messages
>> > in repository log referring to "revision added by local and skipped" -
>> my
>> > specif question is: these revisions are really skipped in a case like
>> this
>> > or restarting from a minor revision it will reload them all? In other
>> works,
>> > Server1 will read and reload all self Server1 revisions or skip them
>> and
>> > read only Server2 revisions?
>> that's also my understanding of how clustering works. but maybe dominique
>> can
>> jump in and correct me if I'm wrong here.
> This is exactly what will happen: a cluster node will always ignore
> entries it has made itself.
> Kind regards
> Dominique

View this message in context: http://www.nabble.com/%3E-Indexes-Backup-tf4805240.html#a13830816
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message