Shawn,
As you mentioned, it was indeed a problem with my network. The port 2888 was
blocked restricting zookeeper communication its peers.
Thanks,
Abhi
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
On 2/23/2019 2:29 PM, abhishek_itengg wrote:
1) I verified the presence of solr.xml file at SOLR_HOME directory on all
the three servers.
2) I am starting the SOLR nodes in the cloud mode. Its configured as NSSM
windows service.
solr start -cloud -f -p 8983 -z
Hi Erick,
1) I verified the presence of solr.xml file at SOLR_HOME directory on all
the three servers.
2) I am starting the SOLR nodes in the cloud mode. Its configured as NSSM
windows service.
solr start -cloud -f -p 8983 -z
"10.**.**.208:2181,10.**.37.**:2181,10.**.38.**:2181"
Everything was
Hi Frankie,
Excuse my ignorance here as I am really new to the ZK and SolrCloud world.
Could you guide me where can I see the ZK logs, I really do not see any
folder for logs in zookeeper directory.
Thanks,
Abhi
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Edwin,
No, the 3 solr nodes are each of an individual server tied with their own
zookeeper instance. So basically 1ZK +1Solr Node instance on each three
servers.
Thanks,
Abhi
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Is your setup of the 3 Solr nodes all on the same server?
Normally we will use dedicated zookeeper and not the embedded one,
especially when you already have 3 nodes, makes more sense to use dedicated
zookeeper.
Regards,
Edwin
On Sun, 24 Feb 2019 at 00:40, Jörn Franke wrote:
> I would not go
I would not go for embedded ZooKeeper, but a dedicated zookeeper - ideally on
different machines than the solr servers.
Check also the ZK logs - maybe the data got corrupted due to improper shutdown.
> Am 23.02.2019 um 17:20 schrieb abhishek_itengg :
>
> Facing an issue where SolrCloud
solr.xml lives in one of two places:
1> SOLR_HOME, and if this was working before, it means that that file was
removed somehow. Solr would not remove it by itself
2> ZooKeeper, in which case if some instances started and some didn’t, you’re
either starting Solr differently or not pointing to
Facing an issue where SolrCloud cluster fails to initialize or come back up
post restart of the servers. I have a solrcloud setup with 3 solr nodes with
embedded zookeeper. Had to restart the servers due to windows patching.
Below is the error I get:-
HTTP ERROR 500
Problem accessing /solr/.
