Hello,
I just built solr.war from trunk and deployed it to a multicore solr server
whose solr.xml looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
<cores adminPath="/admin/cores">
<core name="core0" instanceDir="/mnt/solrhome/cores/core0" />
<core name="core1" instanceDir="/mnt/solrhome/cores/core1" />
</cores>
</solr>
Each core has conf and data/index dirs under its instanceDir.
e.g.
$ tree /mnt/solrhome/cores/core0
cores/core0
|-- conf
| |-- schema.xml -> ../../../conf/schema-foo.xml
| `-- solrconfig.xml -> ../../../conf/solrconfig-foo.xml
`-- data
`-- index
I noticed that when I start the container with this brand new Solr all of a
sudden the '/mnt' directory shows up in /mnt/solrhome !
(this /mnt/solrhome is also the directory from which I happened to start the
container, though I'm not sure if that matters).
This is what this /mnt/solrhome/mnt looks like:
$ tree /mnt/solrhome/mnt
mnt
`-- solrhome
`-- cores
|-- core0
| `-- data
| `-- index
| |-- segments.gen
| `-- segments_1
|-- core1
| `-- data
| `-- index
| |-- segments.gen
| `-- segments_1
So it looks like Solr decides to create the index dir and the full path ot it
there. It looks almost like Solr is looking at my instanceDirs in solr.xml and
decides that it needs to create those directories, but under Solr home dir (I
use -Dsolr.solr.home=/mnt/solrhome).
I switched back to the old solr.war and this stopped happening.
Is this a bug or a new feature that I missed?
Thank you,
Otis
