Re: Queries on Lucene Replication Approach
Adrien Grand <[email protected]> Mon, 25 Aug 2025 17:36:31 +0200
| Newsgroups | gmane.comp.jakarta.lucene.user |
|---|---|
| Message-ID | <CAPsWd+PKU+7D5_DrtvB9=qyETuJhXDj+XKCSwnqvRX+25rgXrg@mail.gmail.com> |
--000000000000a0d34d063d3252f1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 updates to the index. What is NRTLuceneReplication? I cannot find references to it. Lucene's replicator module does have NRT (near-realtime) support through: https://lucene.apache.org/core/10_2_0/replicator/org/apache/lucene/replicat= or/nrt/package-summary.html . On Mon, Aug 25, 2025 at 5:18=E2=80=AFPM sandy A <[email protected]= m> wrote: > 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 are any potential risks (e.g., partial > copies, consistency issues) or best practices recommended for such > approaches. > > *Query 2:* > I noticed that *NRTLuceneReplication* is still marked as "in development.= " > Could you please clarify why it is not yet considered production-ready? A= re > there known limitations or stability concerns that we should be aware of > before experimenting with it? > > Any insights or suggestions would be really helpful. > > > With Regards, > SanthoshKumar A > --=20 Adrien --000000000000a0d34d063d3252f1--