Hi
i am from the same team of Tamer who initiated this thread
We are indexing documents using apache lucene using several parallel
indexing pipelines(java process) to NFS mounted directory.
All of them follows same code and workflow most of the pipelines succeeds
without any issue, but only only
Hi
i am from the same team of Tamer who initiated this thread
We are indexing documents using apache lucene using several parallel
indexing pipelines(java process) to NFS mounted directory.
All of them follows same code and workflow most of the pipelines succeeds
without any issue, but only only
Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Sachin909
> Sent: Wednesday, October 14, 2020 9:43 AM
> To: java-user@lucene.apache.org
> Subject: RE: stucked indexing process
>
> Hi Uwe,
>
> I have observed the similer issue with my
Hi Uwe,
I have observed the similer issue with my application.
Application stack:
"coreLoadExecutor-4-thread-1" #86 prio=5 os_prio=0 tid=0x7fbb1c364800
*nid=0x1616* runnable [0x7fbaa96ef000]
java.lang.Thread.State: RUNNABLE
at sun.nio.fs.UnixNativeDispatcher.stat0(Native Met
apache.org; Uwe Schindler
Subject: Re: stucked indexing process
thanks Uwe for reply. we are indexing data in a cluster where there are
many mount points so it is possible that one them has issue or slowness
when this check first tried but now when i execute "mount" it is
responding all
che.org; Uwe Schindler
> Subject: Re: stucked indexing process
>
> thanks Uwe for reply. we are indexing data in a cluster where there are
> many mount points so it is possible that one them has issue or slowness
> when this check first tried but now when i execute "mount" it
thanks Uwe for reply. we are indexing data in a cluster where there are
many mount points so it is possible that one them has issue or slowness
when this check first tried but now when i execute "mount" it is
responding all the mount points.
I was wondering is there any configuration to skip t
Hi,
to figure out if you system is using an SSD drive for the index directory, the
merge scheduler has to get the underlying mount point of the index directory.
As there is no direct lookup for that, it needs to list all mount points in the
system with a Java7 FS function. And that seems to
