I've never seen lib directives nested, I doubt they're necessary
and it's vaguely possible that this is not intentionally supported.
I'd try un-nesting them personally.
Best
Erick
On Thu, May 3, 2012 at 10:35 AM, <loc...@mm.st> wrote:
>
>
> On Wed, May 2, 2012, at 02:16 PM, Robert Petersen wrote:
>> I don't know if this will help but I usually add a dataDir element to
>> each cores solrconfig.xml to point at a local data folder for the core
>> like this:
>
> after a bit of digging, your suggestion PLUS a change to the 'lib dir'
> specifications in each core's solrconfig.xml
>
> vi solrconfig.xml
>
> ...
> <lib dir="./lib">
> <lib dir="./contrib/extraction/lib">
> <lib dir="./contrib/clustering/lib/">
> <lib
> dir="./contrib/velocity/lib">
> </lib>
> </lib>
> </lib>
> </lib>
> ...
> <dataDir>${solr.data.dir:/srv/www/solrbase/data}</dataDir>
> ...
>
> did the trick. i've a multicore setup working now. thanks!
>
> tbh, i'm not at all sure why the *nested* <lib ...> stanza is used (i
> just lifted it from an example I found online ...), but it seems to
> work.
