lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: SolrCloud Config file
Date Tue, 12 Apr 2016 03:40:15 GMT
Do note by the way that as of Solr 5.5, the bin/solr script has an
option for uploading and downloading configsets. Try typing

bin/solr zk -help

Best,
Erick

On Mon, Apr 11, 2016 at 6:30 PM, Shawn Heisey <apache@elyograg.org> wrote:
> On 4/11/2016 6:40 PM, Sam Xia wrote:
>> Where is the path of topic collection zookeeper config file? Here is from
>> wiki (see below). But I was not able to find configs/topic anywhere in the
>> installation folder.
>
> The /configs/topic path is *inside the zookeeper database*.  It is not a
> path on the filesystem at all.  Zookeeper is a separate Apache project
> that Solr happens to use when running in cloud mode.
>
> http://zookeeper.apache.org/
>
>> "The create command will upload a copy of the data_driven_schema_configs
>> configuration directory to ZooKeeper under /configs/mycollection. Refer to
>> the Solr Start Script Reference
>> <https://cwiki.apache.org/confluence/display/solr/Solr+Start+Script+Referen
>> ce> page for more details about the create command for creating
>> collections.”
>>
>> Here is the command that I run and verify zookeeper is in port 8983. BTW,
>> I did not modify anything and the Solr is a clean install so I do not know
>> why Python is used in the script. The error looks to me that the config
>> folder was not created at first command. So when you try to update it, it
>> gets an IO error.
>>
>> ./solr status
>>
>> Found 2 Solr nodes:
>>
>> Solr process 30976 running on port 7574
>> {
>>   "solr_home":"/locm/solr-6.0.0/example/cloud/node2/solr",
>>   "version":"6.0.0 48c80f91b8e5cd9b3a9b48e6184bd53e7619e7e3 - nknize -
>> 2016-04-01 14:41:49",
>>   "startTime":"2016-04-11T23:42:59.513Z",
>>   "uptime":"0 days, 0 hours, 51 minutes, 43 seconds",
>>   "memory":"93.2 MB (%19) of 490.7 MB",
>>   "cloud":{
>>     "ZooKeeper":"localhost:9983",
>>     "liveNodes":"2",
>>     "collections":"2"}}
>>
>>
>> Solr process 30791 running on port 8983
>> {
>>   "solr_home":"/locm/solr-6.0.0/example/cloud/node1/solr",
>>   "version":"6.0.0 48c80f91b8e5cd9b3a9b48e6184bd53e7619e7e3 - nknize -
>> 2016-04-01 14:41:49",
>>   "startTime":"2016-04-11T23:42:54.041Z",
>>   "uptime":"0 days, 0 hours, 51 minutes, 49 seconds",
>>   "memory":"78.9 MB (%16.1) of 490.7 MB",
>>   "cloud":{
>>     "ZooKeeper":"localhost:9983",
>>     "liveNodes":"2",
>>     "collections":"2"}}
>
> 8983 is a *Solr* port.  The default embedded zookeeper port is the first
> Solr port in the cloud example plus 1000, so it usually ends up being 9983.
>
>> If you run the following steps, you would be able to reproduce the issue
>> every time.
>>
>> Step 1) bin/solr start -e cloud -noprompt
>> Step 2) bin/solr create -c topic -d sample_techproducts_configs
>> Step 3) ./zkcli.sh -cmd upconfig -zkhost localhost:9983 -confname topic
>> -solrhome /locm/solr-5.5.0/ -confdir
>> /locm/solr-5.5.0/server/solr/configsets/sample_techproducts_configs/conf
>
> The "-solrhome" option is not something you need.  I have no idea what
> it will do, but it is not one of the options for upconfig.
>
> I tried this (on Windows) and I'm getting a different problem on the
> upconfig command trying to connect to zookeeper:
>
> https://www.dropbox.com/s/c65zmkhd0le6mzv/upconfig-error.png?dl=0
>
> Trying again on Linux, I had zero problems with the commands you used,
> changing only minor details for the upconfig command (things are in a
> different place, and I didn't use the unnecessary -solrhome option):
>
> https://www.dropbox.com/s/edoa07anmkkep0l/xia-recreate1.png?dl=0
> https://www.dropbox.com/s/ad5ukuvfvlgwq0z/xia-recreate2.png?dl=0
> https://www.dropbox.com/s/ay1u3jjuwy5t52s/xia-recreate3.png?dl=0
>
> Your stated commands indicate 5.5.0, but the JSON status information
> above and the paths they contain indicate that it is 6.0.0 that is
> responding.  I will have to try 6.0.0 later.
>
> If nothing has changed, then "get-pip.py" would not be there.  There
> isn't a configset named "topic_configs_ori" included with Solr, not even
> in the 6.0.0 version.  This came from somewhere besides the Solr website.
>
> Thanks,
> Shawn
>

Mime
View raw message