Hi,
If the index size on disk is about 750 GiB then a memory usage of 2.3 G heap
space for the FST seems fine. It's just a bit strange that you only have 10
million documents!
Are those documents huge and have lots of indexed text content, possibly
OCR/scanned stuff? If this is the case, the t
Hi, Uwe
Thanks for your timely reply. Yes, those documents are huge text. We
have ten indices, and each of them has approximate 75G index size on disk.
Following is the directory content of one of the indices.
Thanks & Best Regards!
lubin
total 74G
-rw-r--r-- 1 root root 100K Jan 10 16:11 _2
Hi lubin,
the terms dictionary is using the "tim" and "tip" files. It should be
approximately in the dimension of the FST.
Do you have all indexes running in the same JVM or is it 10 servers? Because
then the numbers look correct. If you really want to have such an large index
in a single mach
Hi, Uwe
Yes, All indexes running in the same JVM with 14GiB of heap space, but
the JVM heap usage is up to 95%. I'am sue that all
IndexReaders/IndexSearchers has been closed properly.
On 11 January 2018 at 20:46, Uwe Schindler wrote:
> Hi lubin,
>
> the terms dictionary is using the "tim" a
Steve,
Thanks for looking into this. I see the artifacts for 7.2.1-SNAPSHOT,
7.3.0-SNAPSHOT, and 8.0.0-SNAPSHOT are now available so things are looking
good.
--Terry
On Tue, Jan 9, 2018 at 4:38 PM, Uwe Schindler wrote:
> Hi Steve,
>
> If this fixed it could you please add it as dependency on
> On Jan 11, 2018, at 11:18 AM, Terry Smith wrote:
>
> Steve,
>
> Thanks for looking into this. I see the artifacts for 7.2.1-SNAPSHOT,
> 7.3.0-SNAPSHOT, and 8.0.0-SNAPSHOT are now available so things are looking
> good.
Cool, thanks for checking on it.
> On Tue, Jan 9, 2018 at 4:38 PM, Uwe S
