You can call it via curl and it is no more complicated then zk- in the long run 
you will be happier 

> Am 19.11.2019 um 13:27 schrieb Michael Becker <mbec...@ipcoop.com>:
> 
> Jörn,
> 
> We're using Solr to index a website. Basically, we set up Solr and Zookeeper 
> once and let it run. The API is a bit too much overhead for something we just 
> set once.
> 
> Mike
> 
> -----Original Message-----
> From: Jörn Franke <jornfra...@gmail.com>
> Sent: Tuesday, November 19, 2019 2:54 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Zk upconfig command is appending local directory to default 
> confdir
> 
> I would use the config set API - it is more clean for production deployments 
> and you do not have to deal with the zkCli script:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_solr_guide_7-5F4_configsets-2Dapi.html&d=DwIFaQ&c=mV61MqUbMWY-LlirxZJvJg&r=8W5Kk7fJg_C2taHlYyXZLinEFeEtcUcFddYrS5aUhiE&m=czV2n50m-v9_w3N63i-jYUsBfnCtCKeE3wNXq3KVerU&s=8GQix9ABHkY0tm7kPKL_GEXCi-G4PKRjJjN-FqQcRVI&e=
>  
> 
>> Am 18.11.2019 um 15:48 schrieb Michael Becker <mbec...@ipcoop.com>:
>> 
>> I’ve run into an issue when attempting to configure Zookeeper. When running 
>> the zk upconfig -d command specifying a local directory where the 
>> solrconfig.xml files are located, I get the following error:
>> “Could not complete upconfig operation for reason: Could not find 
>> solrconfig.xml at /opt/solr-6.5.1/server/solr/configsets/solrconfig.xml, 
>> /opt/solr-6.5.1/server/solr/configsets/conf/solrconfig.xml or 
>> /opt/solr-6.5.1/server/solr/configsets/ <path to local directory> 
>> /solrconfig.xml”
>> 
>> I’m trying to determine why the solr zk upconfig command is appending 
>> my local directory to the default confdir, rather than looking for the XML 
>> files in that directory, I have two other environments with Solr where this 
>> does not occur. It’s just this one environment that is having this issue.
>> I am using Solr version 6.5.1.
>> Any suggestions on how to troubleshoot this would be appreciated.
>> 
>> Mike

Reply via email to