lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [lucenenet] yashhema opened a new issue #401: Lucene Replication - Geting revision from replicator (local) and handler (remote)
Date Tue, 12 Jan 2021 17:10:59 GMT

yashhema opened a new issue #401:

   I am studying Lucene replication for my understanding .  Lets consider case server A is
the master and server B is the slave.
   I have indexA1, indexA2 on server A which I want to replicate to Server B
   -- On Server A - Any time i make changes to index A1 or indexA2 , i call Replicator.Publish(new
IndexRevision(_writer))  for the corresponding index. Here Replicator represents local replicator
(there will be 2 local replicator - as I want to replicate 2 indexes)
   -- On  Server B - I will create a replication client , passing it to http replicator, IndexReplicationHandler
and persessionfactor , and then I can ask replicationclient to get data from server A  (as
i have 2 indexes to replicate - I will start 2 clients) .
   Question -
   1  -- Is my understanding correct.
   2   -- How can i know the current status of replication , i thought , I can use the field
= Version , which is present in both localreplicator and IndexReplicationHandler , and I can
know if  the replicated copy is at the same version as master copy, but the field is private
-- Is there any reason for keeping it private  
   3   -- To keep things simple, say I only do batch updates in server A , i manually start
the replication on ServerB (with updatenow call) , how can I know that replication copy has
   I think , having point 2 and 3 , will give greater control to the developer in planning
his replication strategy (as well as how to handle failover/recovery from failover better)

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