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 "Buttler, David" <bu...@llnl.gov> on 2012/08/22 21:14:05 UTC
Cloud assigning incorrect port to shards
Hi,
I have set up a Solr 4 beta cloud cluster. I have uploaded a config directory, and linked it with a configuration name.
I have started two solr on two computers and added a couple of shards using the Core Admin function on the admin page.
When I go to the admin cloud view, the shards all have the computer name and port attached to them. BUT, the port is the default port (8983), and not the port that I assigned on the command line. I can still connect to the correct port, and not the reported port. I anticipate that this will lead to errors when I get to doing distributed query, as zookeeper seems to be collecting incorrect information.
Any thoughts as to why the incorrect port is being stored in zookeeper?
Thanks,
Dave
RE: Cloud assigning incorrect port to shards
Posted by "Buttler, David" <bu...@llnl.gov>.
I think the issue was that I didn't have a solr.xml in the solr home. I was a little confused by the example directory because there are actually 5 solr.xml files
% find . -name solr.xml
./multicore/solr.xml
./example-DIH/solr/solr.xml
./exampledocs/solr.xml
./contexts/solr.xml
./solr/solr.xml
Creating my own jetty installation directory without the example instances led to me deleting the solr/solr.xml file.
I have now created a new solr home and set up a solr.xml file there, and things look much better.
Thanks for the feedback,
Dave
-----Original Message-----
From: Mark Miller [mailto:markrmiller@gmail.com]
Sent: Thursday, August 23, 2012 6:00 PM
To: solr-user@lucene.apache.org
Subject: Re: Cloud assigning incorrect port to shards
Can you post your solr.xml file?
On Thursday, August 23, 2012, Buttler, David wrote:
> I am using the jetty container from the example. The only thing I
> have done is change the schema to match up my documents rather than
> the example
>
> -----Original Message-----
> From: Mark Miller [mailto:markrmiller@gmail.com <javascript:;>]
> Sent: Wednesday, August 22, 2012 5:50 PM
> To: solr-user@lucene.apache.org <javascript:;>
> Subject: Re: Cloud assigning incorrect port to shards
>
> What container are you using?
>
> Sent from my iPhone
>
> On Aug 22, 2012, at 3:14 PM, "Buttler, David"
> <buttler1@llnl.gov<javascript:;>>
> wrote:
>
> > Hi,
> > I have set up a Solr 4 beta cloud cluster. I have uploaded a config
> directory, and linked it with a configuration name.
> >
> > I have started two solr on two computers and added a couple of
> > shards
> using the Core Admin function on the admin page.
> >
> > When I go to the admin cloud view, the shards all have the computer
> > name
> and port attached to them. BUT, the port is the default port (8983),
> and not the port that I assigned on the command line. I can still
> connect to the correct port, and not the reported port. I anticipate
> that this will lead to errors when I get to doing distributed query,
> as zookeeper seems to be collecting incorrect information.
> >
> > Any thoughts as to why the incorrect port is being stored in zookeeper?
> >
> > Thanks,
> > Dave
>
--
- Mark
http://www.lucidimagination.com
Re: Cloud assigning incorrect port to shards
Posted by Mark Miller <ma...@gmail.com>.
Can you post your solr.xml file?
On Thursday, August 23, 2012, Buttler, David wrote:
> I am using the jetty container from the example. The only thing I have
> done is change the schema to match up my documents rather than the example
>
> -----Original Message-----
> From: Mark Miller [mailto:markrmiller@gmail.com <javascript:;>]
> Sent: Wednesday, August 22, 2012 5:50 PM
> To: solr-user@lucene.apache.org <javascript:;>
> Subject: Re: Cloud assigning incorrect port to shards
>
> What container are you using?
>
> Sent from my iPhone
>
> On Aug 22, 2012, at 3:14 PM, "Buttler, David" <buttler1@llnl.gov<javascript:;>>
> wrote:
>
> > Hi,
> > I have set up a Solr 4 beta cloud cluster. I have uploaded a config
> directory, and linked it with a configuration name.
> >
> > I have started two solr on two computers and added a couple of shards
> using the Core Admin function on the admin page.
> >
> > When I go to the admin cloud view, the shards all have the computer name
> and port attached to them. BUT, the port is the default port (8983), and
> not the port that I assigned on the command line. I can still connect to
> the correct port, and not the reported port. I anticipate that this will
> lead to errors when I get to doing distributed query, as zookeeper seems to
> be collecting incorrect information.
> >
> > Any thoughts as to why the incorrect port is being stored in zookeeper?
> >
> > Thanks,
> > Dave
>
--
- Mark
http://www.lucidimagination.com
RE: Cloud assigning incorrect port to shards
Posted by "Buttler, David" <bu...@llnl.gov>.
I am using the jetty container from the example. The only thing I have done is change the schema to match up my documents rather than the example
-----Original Message-----
From: Mark Miller [mailto:markrmiller@gmail.com]
Sent: Wednesday, August 22, 2012 5:50 PM
To: solr-user@lucene.apache.org
Subject: Re: Cloud assigning incorrect port to shards
What container are you using?
Sent from my iPhone
On Aug 22, 2012, at 3:14 PM, "Buttler, David" <bu...@llnl.gov> wrote:
> Hi,
> I have set up a Solr 4 beta cloud cluster. I have uploaded a config directory, and linked it with a configuration name.
>
> I have started two solr on two computers and added a couple of shards using the Core Admin function on the admin page.
>
> When I go to the admin cloud view, the shards all have the computer name and port attached to them. BUT, the port is the default port (8983), and not the port that I assigned on the command line. I can still connect to the correct port, and not the reported port. I anticipate that this will lead to errors when I get to doing distributed query, as zookeeper seems to be collecting incorrect information.
>
> Any thoughts as to why the incorrect port is being stored in zookeeper?
>
> Thanks,
> Dave
Re: Cloud assigning incorrect port to shards
Posted by Mark Miller <ma...@gmail.com>.
What container are you using?
Sent from my iPhone
On Aug 22, 2012, at 3:14 PM, "Buttler, David" <bu...@llnl.gov> wrote:
> Hi,
> I have set up a Solr 4 beta cloud cluster. I have uploaded a config directory, and linked it with a configuration name.
>
> I have started two solr on two computers and added a couple of shards using the Core Admin function on the admin page.
>
> When I go to the admin cloud view, the shards all have the computer name and port attached to them. BUT, the port is the default port (8983), and not the port that I assigned on the command line. I can still connect to the correct port, and not the reported port. I anticipate that this will lead to errors when I get to doing distributed query, as zookeeper seems to be collecting incorrect information.
>
> Any thoughts as to why the incorrect port is being stored in zookeeper?
>
> Thanks,
> Dave