lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [lucenenet] mypolat commented on issue #382: Replicator doesn't work
Date Tue, 03 Nov 2020 13:42:11 GMT

mypolat commented on issue #382:

   > First and foremost, you probably need to describe your scenario a bit more so we know
what you are trying to achieve over all, as it stands there is a few things that goes against
common recommendations. Also for what is described in
it really only provides the most basic example so that people can get started using the replicator.
   > I don't know if this crude sample can help you:
   > It uses a class called DataIngestSimulator to simulate changes over time to each index.
(An update to a random number of documents each 30 seconds).
   > When you say that the user can dynamically index, what do you exactly mean?... Are
you simply trying to provide the users with Real-time search, as in the user may update a
document/an entity of some sort which you then want to index and make available right away?
or are you referring to something else?
   > You should avoid recreating your Index writers unless they experience an error (e.g.
OutOfMemmoryExceptions) and share them across all indexing, (That is one writer Per index
in your case).
   The project you created has been very useful for me, thank you.  I completed my shortcomings
from there. My project is working as I want right now.
   So is the scenario below possible with Lucene .Net?
   A master, slave B and C
   B master, slave A and C
   C master, slave A and B
   There will be always 2 copies.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message