lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Riccardo Tasso <riccardo.ta...@gmail.com>
Subject Re: Replicator and Writer deletion policy
Date Thu, 01 Jun 2017 10:48:16 GMT
Thank you Michael, I'm waiting for the Shai answer.

Unfortunately I can't move from lucene4 but I will take a look at the new
NRT replication.

2017-06-01 12:34 GMT+02:00 Michael McCandless <lucene@mikemccandless.com>:

> Sorry, I don't know the answer to your questions; maybe Shai Erera does?
>
> But, FYI: Lucene added near-real-time replication recently (
> https://issues.apache.org/jira/browse/LUCENE-5438), for much faster
> replication (no commit needed).  It also doesn't require you to use
> SnapshotDeletionPolicy.  Instead, the implementation takes care of
> incRef/decRef the files that still need to be copied.
>
> I'm using this feature now and it's working quite well.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Jun 1, 2017 at 3:25 AM, Riccardo Tasso <riccardo.tasso@gmail.com>
> wrote:
>
>> I am studying a solution which uses lucene replicator components (I'm on
>> lucene 4.10.4) and I've found some documentation on the javadoc and in
>> some
>> blog posts.
>>
>> When my IndexWriter commits it produces a Revision which is sent to the
>> ReplicationClient.
>>
>> To be sure of keeping data untill the replica is finished I've set the
>> SnapshotDeletionPolicy for my IndexWriter. Anyway I am observing the
>> growth
>> of the master index while the replica remains much smaller.
>>
>> Should I explicity release my Revision? Which is the right moment to do
>> it?
>>
>> Thanks,
>>  Riccardo
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message