On 3/29/2018 12:45 PM, Abhi Basu wrote:
> Also, another question, where it says to copy the zoo.cfg from
> /solr72/server/solr folder to /solr72/server/solr/node1/solr, should I
> actually be grabbing the zoo.cfg from one of my external zk nodes?
If you're using zookeeper processes that are separa
Just an update. Adding hostnames to solr.xml and using "-z
zk1:2181,zk2:2181,zk3:2181" worked and I can see 4 live nodes and able to
create collection with 2S/2R.
Thanks for your help, greatly appreciate it.
Regards,
Abhi
On Thu, Mar 29, 2018 at 1:45 PM, Abhi Basu <9000r...@gmail.com> wrote:
>
Also, another question, where it says to copy the zoo.cfg from
/solr72/server/solr folder to /solr72/server/solr/node1/solr, should I
actually be grabbing the zoo.cfg from one of my external zk nodes?
Thanks,
Abhi
On Thu, Mar 29, 2018 at 1:04 PM, Abhi Basu <9000r...@gmail.com> wrote:
> Ok, will
Ok, will give it a try along with the host name.
On Thu, Mar 29, 2018 at 12:20 PM, Webster Homer
wrote:
> This Zookeeper ensemble doesn't look right.
> >
> > ./bin/solr start -cloud -s /usr/local/bin/solr-7.2.1/server/solr/node1/
> -p
> > 8983 -z zk0-esohad,zk1-esohad,zk3-esohad:2181 -m 8g
>
>
This Zookeeper ensemble doesn't look right.
>
> ./bin/solr start -cloud -s /usr/local/bin/solr-7.2.1/server/solr/node1/ -p
> 8983 -z zk0-esohad,zk1-esohad,zk3-esohad:2181 -m 8g
Shouldn't the zookeeper ensemble be specified as:
zk0-esohad:2181,zk1-esohad:2181,zk3-esohad:2181
You should put the
I had that problem. Very annoying and we probably should require special flag
to use localhost.
We need to start solr like this:
./solr start -c -h `hostname`
If anybody ever forgets, we get a 127.0.0.1 node that shows down in cluster
status. No idea how to get rid of that.
wunder
Walter Unde
So, in the solr.xml on each node should I set the host to the actual host
name?
${host:}
${jetty.port:8983}
${hostContext:solr}
${genericCoreNodeNames:true}
${zkClientTimeout:3}
${distribUpdateSoTimeout:60}
${distribUpdateConnTimeout:6}
${zkCrede
On 3/29/2018 8:25 AM, Abhi Basu wrote:
"Operation create caused
exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Cannot create collection ems-collection. Value of maxShardsPerNode is 1,
and the number of nodes currently live or live and part of your
I'm be
Yes, only showing one live node on admin site.
Checking zk logs.
Thanks,
Abhi
On Thu, Mar 29, 2018 at 9:32 AM, Ganesh Sethuraman
wrote:
> may be you can check int he Admin UI --> Cloud --> Tree --> /live_nodes. To
> see the list of live nodes before running. If it is less than what you
> expe
may be you can check int he Admin UI --> Cloud --> Tree --> /live_nodes. To
see the list of live nodes before running. If it is less than what you
expected, check the Zoo keeper logs? or make sure connectivity between the
shards and zookeeper.
On Thu, Mar 29, 2018 at 10:25 AM, Abhi Basu <9000r...@
What am I missing? I used the following instructions
http://blog.thedigitalgroup.com/susheelk/2015/08/03/solrcloud-2-nodes-solr-1-node-zk-setup/#comment-4321
on 4 nodes. The only difference is I have 3 external zk servers. So this
is how I am starting each solr node:
./bin/solr start -cloud -s /u
11 matches
Mail list logo
