Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of guksunm@gmail.com designates
 209.85.219.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEY5pxW2Cgf=s0xQ9fUmWju5yHXyqFY-+D6-qjyEo2rYKEHbqw@mail.gmail.com>
References: 
 <CAKDTq=PA7GpWKQm3K1p=JbhFhA6xwRehdw_if66b+TN=1_r9HA@mail.gmail.com>
	<CAEY5pxW2Cgf=s0xQ9fUmWju5yHXyqFY-+D6-qjyEo2rYKEHbqw@mail.gmail.com>
Date: Thu, 10 Jul 2014 10:55:24 +0900
Message-ID: 
 <CAKDTq=MrXOg1aBhbjLT-obrBZ5LjPYDE4e2QZOXFGTKVsBCCcA@mail.gmail.com>
Subject: Re: IndexSearcher.doc thread safe problem
From: =?UTF-8?B?6rmA7ISg66y0KHN1bm1vbywgS0lNKQ==?= <guksunm@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001a11330d023dfb4404fdcd1e08

--001a11330d023dfb4404fdcd1e08
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks answer Ian

I more check this problem..(Lucene 4.8.1)

1. acceptsDocsOutOfOrder() return false
    =3D=3D> ineffective

2. acceptsDocsOutOfOrder() return true
    =3D=3D> ineffective

3. ConncurrentLinkedQueue add() and poll() methods check value in
multi-thread
    =3D=3D> the queue is no problem.

4. Syncronized searcher.doc method call in multi-thread(like this: public
synchronized Document getValue( IndexSearcher searcher, int docId ) {
return searcher.doc( docId ); })
    =3D=3D> every execution is same.
           but If I use this method, It is no difference with single thread
performance.

What do you think about it?

Thanks


2014-07-10 2:04 GMT+09:00 Ian Lea <ian.lea@gmail.com>:

> It's more likely to be a demonstration that concurrent programming is
> hard, results often hard to predict and debugging very hard.
>
> Or perhaps you simply need to add acceptsDocsOutOfOrder() to your
> collector, returning false.
>
> Either way, hard to see any evidence of a thread-safety problem in lucene=
.
>
> If adding acceptsDocsOutOfOrder() doesn't fix it, I suggest you verify
> that your queue is getting the values you expect, in the order you
> expect, consistently.  Then worry about the display part, first
> checking everything without any lucene calls.
>
>
> --
> Ian.
>
> On Wed, Jul 9, 2014 at 5:59 AM, =EA=B9=80=EC=84=A0=EB=AC=B4 <guksunm@gmai=
l.com> wrote:
> > Hi all,
> >
> > I know IndexSearcher is thread safe.
> > But IndexSearcher.doc is not thread safe maybe...
> >
> > I try to below
> > --------------------------------------------
> > First, I extract docID at index directory. And that docID add on
> > queue(ConcurrentLinkedQueue)
> >
> > Second, extract field value using docID poll at this queue after extrac=
t
> > process end. This process is  work to multi-threads.
> >
> > For this I used the following summation code below:
> > searcher.search( query, filter, new Collector() { public void collect(
> int
> > doc ) { queue.add( docBase + doc ) } );
> > Thread thread1 =3D new Thread( () -> { while( !queue.isEmpty() ) {
> > System.out.println( searcher.doc(queue.poll()).get("content") ); } } );
> > Thread thread2 =3D new Thread( thread1 );
> > thread1.start();
> > thread2.start();
> > -------------------------------------------
> >
> > Result was different in every execution.
> >
> > My method is wrong? or IndexSearcher bug?
> >
> > Please help me
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--001a11330d023dfb4404fdcd1e08--