In this context I would also note that while copying is progress, an
attempt to open the directory might report a corrupted index due to a
commit not having all of its files available or due to partially copied
files. For example, if your query servers are calling
`DirectoryReader.openIfChanged()`
Hi, we use Lucene NRT replication in production.
For consistent snapshots, we use SnapshotDeletionPolicy to open a snapshot, and
then copy the snapshot'ed
files with your tool of choice like rsync. Without a snapshot, I don't think
such tools work reliably - you can copy
commit metadata without
Hello,
If you can guarantee no concurrent updates while you are doing the copy,
then 3rd-party tools that replicate files such as fsync are fine. But
otherwise or if you have the choice, I would recommend to use Lucene's
built-in support for replication, which can also work if there are
concurrent
Hi Lucene Community Team,
I have a couple of queries related to Lucene replication and would
appreciate your guidance:
*Query 1:*
Is it safe to use tools like *rsync* (on Linux) or *robocopy* (on Windows)
for copying Lucene segment files from one server to another?
I want to understand if there a
