jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shinichiro Abe <shinichiro.ab...@gmail.com>
Subject Re: OakDirectory with cluster
Date Wed, 05 Aug 2015 09:31:51 GMT
Hi Chetan,

Thanks. That means a direct use of RAMDirectory for NRT functionality instead of NRTCachingDirectory,

and using OakDirectory as persistent directory in parallel? It looks like tricky a little
bit for me but an interesting idea.

Thank you very much,
Shinichiro Abe

> 2015/08/05 14:56、Chetan Mehrotra <chetan.mehrotra@gmail.com> のメール:
> Hi Abe-san,
> On Wed, Aug 5, 2015 at 7:48 AM, Shinichiro Abe
> <shinichiro.abe.1@gmail.com> wrote:
>> I saw the discussion that you proposed about NRT searching in Oak a few weeks ago.
>> NRT search requires an IndexWriter which has uncommitted documents in-memory.
>> If users do a NRT searching, do you intend to get the writer from that singleton
writer service?
> My reference to NRT in that thread was bit overloaded usage. What I
> meant was to enable search for data added on same cluster node if the
> user has a session affinity with that node. For e.g. if a cluster
> consist of 2 nodes N1 and N2 and user U1 is always interacting with N1
> i.e. adding new images etc. Then to enable search for images added by
> him on N1 faster the proposal was to keep recently added data in an
> index backed by RAMDirectory. Any query would then consult both
> persistent index and the in mem index.
> User U2 interacting with N2 server would still not be able see changes
> done by U1 on N1.
>> (I don't know how to get the writer from another process.)
> Yup thats not possible.
>> I'm interested in Oak from 1 year ago but didn't take Sling into account until today.
> Sling is just a host application which embeds Oak and Oak relies on
> host application for certain aspects like coordinating the jobs across
> cluster.
> Chetan Mehrotra

View raw message