Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of stachoo@gmail.com designates
 209.85.220.176 as permitted sender)
MIME-Version: 1.0
Sender: stachoo@gmail.com
In-Reply-To: <BANLkTi=fJ5fBkyhxqM-W45sEEmV67+TEuQ@mail.gmail.com>
References: <BANLkTim5RAwvOc9+UfNpLJ_24M4_KeS61A@mail.gmail.com>
	<BANLkTinN4PxZu1eZxA8rUVP+9Bx5vy4PQg@mail.gmail.com>
	<BANLkTimszHMv5sZi7HZgV2a39SW_Qbx1uA@mail.gmail.com>
	<BANLkTi=2b8xemeFK4O=sd-M=61AhtV2R7Q@mail.gmail.com>
	<BANLkTi=fJ5fBkyhxqM-W45sEEmV67+TEuQ@mail.gmail.com>
Date: Fri, 1 Jul 2011 09:45:01 +0200
Message-ID: <BANLkTinmF9pB6TgaPPewFhU=mBnadcOePA@mail.gmail.com>
Subject: Re: Multicore clustering setup problem
From: Stanislaw Osinski <stanislaw.osinski@carrotsearch.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=20cf307f338cf2a4a904a6fd31da

--20cf307f338cf2a4a904a6fd31da
Content-Type: text/plain; charset=ISO-8859-1

Hi Walter,

That makes sense, but this has always been a multi-core setup, so the paths
> have not changed, and the clustering component worked fine for core0. The
> only thing new is I have fine tuned core1 (to begin implementing it).
> Previously the solrconfig.xml file was very basic. I replaced it with
> core0's solrconfig.xml and made very minor changes to it (unrelated to
> clustering) - it's a nearly identical solrconfig.xml file so I'm surprised
> it doesn't work for core1.
>

I'd probably need to take a look at the whole Solr dir you're working with,
clearly there's something wrong with the classpath of core1.

Again, I'm wondering if perhaps since both cores have the clustering
> component, if it should have a shared configuration in a different file
> used
> by both cores(?). Perhaps the duplicate clusteringComponent configuration
> for both cores is the problem?
>

I'm not an expert on Solr's internals related to core management, but I once
did configure two cores with search results clustering, where clustering
configuration and <lib>s were specified for each core separately, so this is
unlikely to be a problem. Another approach would be to put all the JARs
required for clustering in a common directory and point Solr to that lib
using the sharedLib attribute in the <solr> tag:
http://wiki.apache.org/solr/CoreAdmin#solr. But it really should work both
ways.

If you can somehow e-mail (off-list) the listing of your Solr directory and
contents of your configuration XMLs, I may be able to trace the problem for
you.

Cheers,

Staszek

--20cf307f338cf2a4a904a6fd31da--