You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Otis Gospodnetic <ot...@yahoo.com> on 2009/07/14 23:49:19 UTC
Multicore Solr (trunk) creates extra dirs
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
Re: Multicore Solr (trunk) creates extra dirs
Posted by Otis Gospodnetic <ot...@yahoo.com>.
Hi,
Paul and Shalin will know about this. What I'm seeing looks a lot like what Walter reported in March:
* http://markmail.org/thread/dfsj7hqi5buzhd6n
And this commit from Paul seems possibly related:
* http://markmail.org/message/cjvjffrfszlku3ri
...because of things like:
- cores = new CoreContainer(new SolrResourceLoader(instanceDir));
+ cores = new CoreContainer(new SolrResourceLoader(solrHome));
...
if (!idir.isAbsolute()) {
- idir = new File(loader.getInstanceDir(), dcore.getInstanceDir());
+ idir = new File(solrHome, dcore.getInstanceDir());
...
I don't have dataDir in my solr.xml, only absolute paths to my cores.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Otis Gospodnetic <ot...@yahoo.com>
> To: solr-user@lucene.apache.org
> Sent: Tuesday, July 14, 2009 5:49:19 PM
> Subject: Multicore Solr (trunk) creates extra dirs
>
>
> Hello,
>
> I just built solr.war from trunk and deployed it to a multicore solr server
> whose solr.xml looks like this:
>
>
>
>
>
>
>
>
> 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