On 11/19/2018 6:44 AM, Tech Support wrote:
1. If the disk free space is completed, is it possible to configure
another drive? Which means, if C drive free space is over need to configure
the D drive. I need to read the data from both C and D drives.
There is no automated way to do this.
You can quite easily move the dataDir for an individual core. You just
have to find its core.properties file and add/change the dataDir
property in that file to point to a new location, and then reload the
collection after you have done what you need to with the index data.
The dataDir defaults to "data" ... which is relative to the
instanceDir. The default location for the instanceDir is the directory
where core.properties is found.
You seem to be talking about Windows, so you won't be able to just move
the index directory, because Windows will refuse to delete files that a
process has open. You'll need to copy it, reload the collection, and
then you can delete the original. If you have proper redundancy in your
SolrCloud, you could opt to not copy or move the index ... when you
reload the collection, SolrCloud will notice that there is no index in
the new dataDir and copy it for you over the network from the machine
that has the leader role for the shard.
If you're wanting to create a brand new collection with its data on
another drive, you would need to create it in place within the defined
Solr Home, perform the above operation on all of its cores, and then
reload the collection.
If you want to move ALL of your data to another location, you could just
copy all of your cores from the current solr home (which defaults to
server/solr), change the solr home to the new location, and restart Solr.
If this sounds complicated, you're not wrong.
Thanks,
Shawn
