Hi Jorn, I have set the heap size to 6GB, and the system has 32GB of RAM.
The data is indexed from CSV file, so each field's data is like database type of data. Only the searchFields may have more data as it contains the important fields of the collection. But then again it is not as large as things like contents from emails. The index size is currently only 3GB, which shouldn't be considered big to split the collections to different nodes? Regards, Edwin On Fri, 25 Jan 2019 at 20:49, Jörn Franke <jornfra...@gmail.com> wrote: > Have you done a correct sizing wrt to memory / CPU? > > Check also the data model if you have a lot of queried stored fields that > may contain a lot of data. > > You may also split those two collections on different nodes. > > > Am 23.01.2019 um 18:01 schrieb Zheng Lin Edwin Yeo <edwinye...@gmail.com > >: > > > > Hi, > > > > I am using Solr 7.5.0, and currently I am facing an issue of when I am > > indexing in collection2, the indexing affects the records in collection1. > > Although the records are still intact, it seems that the settings of the > > termVecotrs get wipe out, and the index size of collection1 reduced from > > 3.3GB to 2.1GB after I do the indexing in collection2. Also, the search > in > > collection1, which was originall very fast, becomes very slow after the > > indexing is done is collection2. > > > > Anyone has faced such issues before or have any idea on what may have > gone > > wrong? > > > > Regards, > > Edwin >
