If you're able to tell Windows FRS which specific files to copy, then
SnapshotDeletionPolicy (in 2.3) should work for this.
It basically protects a consistent snapshot of your index, ensuring
those files will not be deleted, while not blocking further updates
to the index.
Mike
Ruslan Sivak wrote:
I'm wondering if this is a problem that lucene users have already
tackled. I have four copies of the application using a lucene
index. They are located on two physical servers with two copies on
each server accessing two copies of the lucene index. I use
Windows FRS (File Replication Service) to replicate the index
between the two servers.
Things work well most of the time, but sometimes, I believe under
load, the index doesn't get a chance to propagate before another
write takes place and it gets corrupted.
What would you recommend I use to keep the index in sync between
the four copies of the app?
Russ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
