On 7/12/2017 8:25 PM, Zheng Lin Edwin Yeo wrote:
> Thanks Shawn and Erick.
>
> We are planning to migrate the data in two of the largest collections to
> another hard disk, while the rest of the collections remains at the default
> one for the main core.
> So there are already data indexed in the c
Thanks Shawn and Erick.
We are planning to migrate the data in two of the largest collections to
another hard disk, while the rest of the collections remains at the default
one for the main core.
So there are already data indexed in the collections.
Will this method work, or we have to create a ne
Shawn's way will work, of course you have to be sure you didn't index
any data before editing all the core.properties files.
There's another way to set the dataDir per core though that has the
advantage of not entailing any down time or hand editing files:
> create the collection with createNodeSe
On 7/12/2017 12:38 AM, Zheng Lin Edwin Yeo wrote:
> I found that we can set the path under in solrconfig.xml
>
> However, this seems to work only if there is one replica. How do we set it
> if we have 2 or more replica?
Setting dataDir in solrconfig.xml is something that really only works in
stan
I found that we can set the path under in solrconfig.xml
However, this seems to work only if there is one replica. How do we set it
if we have 2 or more replica?
Regards,
Edwin
On 6 July 2017 at 11:34, Zheng Lin Edwin Yeo wrote:
> Hi,
>
> Would like to check, how can we place the indexed fil
Hi,
Would like to check, how can we place the indexed files of different
collections on different hard disk/folder, but they are in the same node?
For example, I want collection1 to be placed in C: drive, collection2 to be
placed in D: drive, and collection3 to be placed in E: drive.
I am using
