Re: Lower case "or" is being treated as operator OR?

[Chris Hostetter]

: I think by "what query parser" you mean this:

no, that's the fieldType -- what i was refering to is that you are in fact 
using "edismax", but with solr 8.1 lowercaseOperators should default to 
"false", so my initial guess is probably wrong.

: By "request parameter" I think you are asking what I'm sending to Solr?  if
: sow I'm sending it the raw text of "or" or "OR".  In case you mean my
: request-handler, it is this:

i mean all of it -- including any other request params your client may be 
sending to solr that overrides those defaults you just posted.

the best thing to do to make sense of this is add 
"echoParams=all" and "debug=true" to your request, and show us the 
full response, along with some details of what docs in that result you 
don't expect to match, so we can look at:

1) what params come back in the responseHeader, so we can sanity check 
exactly what query string(s) are getting sent to solr, and that 
nothing is overriding lowercaseOperators, etc...

2) what comes back in the query debug section, so we can sanity check how 
your query strings are getting parsed

2) what the "explain" output looks like for those docs you are getting 
that you don't expect, so we can see why they matched.


FWIW: you mentioned "My default operator is AND" ... but that's not 
visible in the requestHandler defaults you posted -- so where is it being 
set?  (maybe it's not being set like you think it is?)



-Hoss
http://www.lucidworks.com/

Re: Lower case "or" is being treated as operator OR?

[Steven White]

Hi Chris,

This is on Sorl 8.1.1

I think by "what query parser" you mean this:

  

  
  
  
  

  

By "request parameter" I think you are asking what I'm sending to Solr?  if
sow I'm sending it the raw text of "or" or "OR".  In case you mean my
request-handler, it is this:

{"requestHandler":{"/select_hcl":{
  "class":"solr.SearchHandler",
  "name":"/select_hcl",
  "defaults":{
"defType":"edismax",
"echoParams":"explicit",
"fl":"CC_UNIQUE_FIELD,CC_FILE_PATH,score",
"indent":"true",
"qf":"CC_ALL_FIELDS_DATA",
"rows":"100",
"wt":"xml"

Yes, I'm using edismax.  So if that's what's causing it, how do I tell it
to treat only uppercase OR and AND as operators?

Thanks in advanced.

Steven


On Wed, Aug 7, 2019 at 7:39 PM Chris Hostetter 
wrote:

>
> what version of solr?
> what query parser are you using?
> what do all of your request params (including defaults) look like?
>
> it's possible you are seeing the effects of edismax's "lowercaseOperators"
> param, which _should_ default to "false" in modern solr, but
> in very old versions it defaulted to "true" (inspite of what the docs at
> the time said)...
>
>
> https://lucene.apache.org/solr/guide/8_1/the-extended-dismax-query-parser.html
> https://issues.apache.org/jira/browse/SOLR-4646
>
>
> : Date: Wed, 7 Aug 2019 19:32:02 -0400
> : From: Steven White 
> : Reply-To: solr-user@lucene.apache.org
> : To: solr-user@lucene.apache.org
> : Subject: Lower case "or" is being treated as operator OR?
> :
> : Hi everyone,
> :
> : My schema is setup to index all words (no stop-words such as "or", "and",
> : etc.) are removed.  My default operator is AND.  But when I search for
> "one
> : or two" (without the quotes as this is not a phrase search) I'm getting
> : hits on documents that have either "one" or "two".  It has the same
> effect
> : as if I searched for "one OR two".  Any idea why?
> :
> : Where should I look to see what's causing this issue?  What part of my
> : schema or request handler do you need to see?
> :
> : In case this helps.  Searching for just "or" or "OR" (with or without
> : quests) gives me the same set of hits and ranking.  The same is also true
> : for "and" or "AND".
> :
> : Thanks.
> :
> : Steven
> :
>
> -Hoss
> http://www.lucidworks.com/
>

Re: Lower case "or" is being treated as operator OR?

[Chris Hostetter]

what version of solr?
what query parser are you using?
what do all of your request params (including defaults) look like?

it's possible you are seeing the effects of edismax's "lowercaseOperators" 
param, which _should_ default to "false" in modern solr, but 
in very old versions it defaulted to "true" (inspite of what the docs at 
the time said)...

https://lucene.apache.org/solr/guide/8_1/the-extended-dismax-query-parser.html
https://issues.apache.org/jira/browse/SOLR-4646


: Date: Wed, 7 Aug 2019 19:32:02 -0400
: From: Steven White 
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Lower case "or" is being treated as operator OR?
: 
: Hi everyone,
: 
: My schema is setup to index all words (no stop-words such as "or", "and",
: etc.) are removed.  My default operator is AND.  But when I search for "one
: or two" (without the quotes as this is not a phrase search) I'm getting
: hits on documents that have either "one" or "two".  It has the same effect
: as if I searched for "one OR two".  Any idea why?
: 
: Where should I look to see what's causing this issue?  What part of my
: schema or request handler do you need to see?
: 
: In case this helps.  Searching for just "or" or "OR" (with or without
: quests) gives me the same set of hits and ranking.  The same is also true
: for "and" or "AND".
: 
: Thanks.
: 
: Steven
: 

-Hoss
http://www.lucidworks.com/

Lower case "or" is being treated as operator OR?

[Steven White]

Hi everyone,

My schema is setup to index all words (no stop-words such as "or", "and",
etc.) are removed.  My default operator is AND.  But when I search for "one
or two" (without the quotes as this is not a phrase search) I'm getting
hits on documents that have either "one" or "two".  It has the same effect
as if I searched for "one OR two".  Any idea why?

Where should I look to see what's causing this issue?  What part of my
schema or request handler do you need to see?

In case this helps.  Searching for just "or" or "OR" (with or without
quests) gives me the same set of hits and ranking.  The same is also true
for "and" or "AND".

Thanks.

Steven

Using custom scoring formula

[Arnold Bronley]

Hi,

I have a topic verctor calculated for each of the Solr document in a
collection. Topic vector is calculated using LDA (
https://en.wikipedia.org/wiki/Latent_Dirichlet_allocation).  Now I want to
return the similar document to a given document from this collection. I can
simply use normalized dot product between the given vector and all other
vectors to see which one has product of ~1. That will tell me that those
are very similar documents. Is there a way to achieve this using Solr?

Re: Issue : Solr Server becoming Un-responsive

[Jörn Franke]

Zookeeper on the same machine? Maybe you take memory from it?

Do you observe swapping? 

Normally your memory should be much larger than heap, because Spark heavily 
uses os caches, which are not on heap.

> Am 07.08.2019 um 15:22 schrieb Abhimeet, Kumar :
> 
> Hi Team,
> 
> 
> 
> We are facing an issue of Solr becoming unresponsive after every 2-3 Hrs. We 
> recently increased the allocated JVM size on Solr up to 11GB, since then the 
> issue is very frequent.
> 
> 
> 
> Current Java Settings on Solr are:
> 
> java -server -Xms11095m -Xmx11095m -XX:NewRatio=3 -XX:SurvivorRatio=4 
> -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC 
> -XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 
> -XX:+CMSScavengeBeforeRemark -XX:PretenureSizeThreshold=64m 
> -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50 
> -XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled 
> -XX:+ParallelRefProcEnabled -XX:-OmitStackTraceInFastThrow -verbose:gc 
> -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps 
> -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution 
> -XX:+PrintGCApplicationStoppedTime 
> -Xloggc:/opt/solr-7.1.0/server/logs/solr_gc.log -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M 
> -Dsolr.log.dir=/opt/solr-7.1.0/server/logs -Djetty.port=8983 -DSTOP.PORT=7983 
> -DSTOP.KEY=solrrocks -Duser.timezone=UTC -Djetty.home=/opt/solr-7.1.0/server 
> -Dsolr.solr.home=/opt/solr-7.1.0/server/solr -Dsolr.data.home= 
> -Dsolr.install.dir=/opt/solr-7.1.0 
> -Dsolr.default.confdir=/opt/solr-7.1.0/server/solr/configsets/_default/conf 
> -Xss256k -Dsolr.jetty.https.port=8983 -Dsolr.log.muteconsole 
> -XX:OnOutOfMemoryError=/opt/solr-7.1.0/bin/oom_solr.sh 8983 
> /opt/solr-7.1.0/server/logs -jar start.jar
> 
> Cache Configs are:
> 
> 
> 
>  
>  size="512"
> 
>  initialSize="512"
> 
>  autowarmCount="0"/>
> 
>  
>  size="512"
> 
>  initialSize="512"
> 
>  autowarmCount="0"/>
> 
>  
>size="512"
> 
>initialSize="512"
> 
>autowarmCount="0"/>
> 
> 
> Find the attached thread dumps. 
> 
> 
> 
> Please help!
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kumar Abhimeet | ICF Next
> Senior Consultant
> c: 080-46409406
> icfolson.com | LinkedIn | Twitter 
> 

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Zheng Lin Edwin Yeo]

I have managed to get it to work.
The issue with the creation of collection is due to the SSL settings.

So now should be able to continue to use as per normal while waiting for
the cosmetic issue to be resolve.
Thank you.

Regards,
Edwin

On Wed, 7 Aug 2019 at 17:07, Zheng Lin Edwin Yeo 
wrote:

> I am using Java version 1.8.0_221.
>
> Ok, I will give it a try.
>
> Regards,
> Edwin
>
> On Wed, 7 Aug 2019 at 14:52, Jan Høydahl  wrote:
>
>> Which Java version are u using? Can you try to reproduce from scratch
>> with a small cluster, no SSL etc, just solr 8.2 & zk 3.5.5 and create
>> collection?
>>
>> Jan Høydahl
>>
>> > 7. aug. 2019 kl. 05:33 skrev Zheng Lin Edwin Yeo > >:
>> >
>> > Hi,
>> >
>> > From my Solr logs, any leads on why the collection creation failed, if
>> the
>> > issue is only a cosmetic issue?
>> >
>> > It can work correctly in this same new version of Solr when I use
>> ZooKeeper
>> > 3.4.14.
>> >
>> > Regards,
>> > Edwin
>> >
>> >
>> >> On Thu, 1 Aug 2019 at 18:05, Jörn Franke  wrote:
>> >>
>> >> For me:
>> >> * ZK stand-alone mode - no issues
>> >> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I
>> >> see the same error message), but aside this Solr is working fine
>> >>
>> >>
>> >>
>> >>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com
>> >>> :
>> >>>
>> >>> Hi Jörn,
>> >>> Thank you for your reply.
>> >>>
>> >>> I have encountered problem when I tried to create a collection with
>> this
>> >>> new version of ZooKeeper. You can find my Solr log file here:
>> >>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>> >>>
>> >>> Does it work perfectly at your side for creating collections and
>> indexing
>> >>> even when running ZooKeeper ensemble?
>> >>>
>> >>> Regards,
>> >>> Edwin
>> >>>
>> >>>
>>  On Thu, 1 Aug 2019 at 17:39, Jörn Franke 
>> wrote:
>> 
>>  I confirm the issue.
>> 
>>  Interestingly it does not happen with ZK standalone, but only in a ZK
>>  Ensemble.
>> 
>>  It seems to be mainly cosmetic in the admin UI because Solr appears
>> to
>>  function normally.
>> 
>> > Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo <
>> >> edwinye...@gmail.com
>> > :
>> >
>> > Yes. You can get my full solr.log from the link below. The error is
>> >> there
>> > when I tried to create collection1 (around line 170 to 300) .
>> >
>> > https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>> >
>> > Regards,
>> > Edwin
>> >
>> >
>> >> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>>  wrote:
>> >>
>> >> Please look for the full log file solr.log in your Solr server, and
>>  share
>> >> it via some file sharing service or gist or similar for us to be
>> able
>> >> to
>> >> decipher the collection create error.
>> >>
>> >> --
>> >> Jan Høydahl, search solution architect
>> >> Cominvent AS - www.cominvent.com
>> >>
>> >>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>>  edwinye...@gmail.com
>> >>> :
>> >>>
>> >>> Hi,
>> >>>
>> >>> Regarding the issue, I have tried to put the following in zoo.cfg
>> >> under
>> >>> ZooKeeper:
>> >>> 4lw.commands.whitelist=mntr,conf,ruok
>> >>>
>> >>> But it is still showing this error.
>> >>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>>  zookeeper
>> >>> configuration file."*
>> >>>
>> >>> As I am using SolrCloud, the collection config can still be
>> loaded to
>> >>> ZooKeeper as per normal. But if I tried to create a collection, I
>> >> will
>> >> get
>> >>> the following error:
>> >>>
>> >>> {
>> >>> "responseHeader":{
>> >>> "status":400,
>> >>> "QTime":686},
>> >>> "failure":{
>> >>> "192.168.1.2:8983
>> >>
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>> >>> occurred when talking to server at:http://192.168.1.2:8983/solr";,
>> >>> "192.168.1.2:8984
>> >>
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>> >>> occurred when talking to server at:http://192.168.1.2:8984/solr
>> "},
>> >>> "Operation create caused
>> >>>
>> >>
>> 
>> >>
>> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>> >>> Underlying core creation failed while creating collection:
>>  collection1",
>> >>> "exception":{f
>> >>> "msg":"Underlying core creation failed while creating collection:
>> >>> collection1",
>> >>> "rspCode":400},
>> >>> "error":{
>> >>> "metadata":[
>> >>>   "error-class","org.apache.solr.common.SolrException",
>> >>>   "root-error-class","org.apache.solr.common.SolrException"],
>> >>> "msg":"Underlying core creation failed while creating collection:
>> >>> collection1",
>> >>> "code":400}}
>> >>>
>> >>> Is there anything which I may have missed out

Re: Query regarding Solr Search

[Shawn Heisey]

On 8/7/2019 6:39 AM, Khare, Kushal (MIND) wrote:

Hello People !
Hope you all are doing good !

Well, I am new to the solr server and want to use it for content search in one 
of my applications.
I have already been working upon it since quite a few days, and have the basics 
done.

The issue that I have is, I want my search to be restricted only upon the 
content and not the metadata. Currently, it return the document if the searched 
query is either in the content or the metadata.
So, please could anyone help me with this, as to how to search on these two 
fields independently.


The basic answer is that you need to adjust the query that you are 
sending to Solr. so that it doesn't search both fields.


To help further, we would have to know more details, including how your 
index is configured and what your queries are.


With default settings, Solr will log all queries to solr.log.  By 
default they are not logged in a way that can be seen from the admin UI. 
 The query logging in solr.log is quite complete, and would probably be 
enough for us to begin looking and know what additional questions we 
might need to ask.


Thanks,
Shawn

Re: Issue : Solr Server becoming Un-responsive

[Shawn Heisey]

On 8/7/2019 7:22 AM, Abhimeet, Kumar wrote:
We are facing an issue of Solr becoming unresponsive after every 2-3 
Hrs. We recently increased the allocated JVM size on Solr up to 11GB, 
since then the issue is very frequent.





Find the attached thread dumps.


I'm amazed that the attachment made it to the list.  They usually don't. 
 Unfortunately, thread dumps may not be all that useful for this.  None 
of them indicate a deadlock, so it's probably a performance problem.


Can you gather the screenshot described at the following URL?

https://cwiki.apache.org/confluence/display/solr/SolrPerformanceProblems#SolrPerformanceProblems-Askingforhelponamemory/performanceissue

It will be critical to make sure the list is sorted as described there.

Don't send the resulting screenshot as an attachment.  It won't make it 
to the list.  You'll need to use a file sharing website and give us the URL.


Thanks,
Shawn

Issue : Solr Server becoming Un-responsive

[Abhimeet, Kumar]

Hi Team,


We are facing an issue of Solr becoming unresponsive after every 2-3 Hrs. We 
recently increased the allocated JVM size on Solr up to 11GB, since then the 
issue is very frequent.


Current Java Settings on Solr are:

java -server -Xms11095m -Xmx11095m -XX:NewRatio=3 -XX:SurvivorRatio=4 
-XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC 
-XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 
-XX:+CMSScavengeBeforeRemark -XX:PretenureSizeThreshold=64m 
-XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50 
-XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled 
-XX:+ParallelRefProcEnabled -XX:-OmitStackTraceInFastThrow -verbose:gc 
-XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps 
-XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution 
-XX:+PrintGCApplicationStoppedTime 
-Xloggc:/opt/solr-7.1.0/server/logs/solr_gc.log -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M 
-Dsolr.log.dir=/opt/solr-7.1.0/server/logs -Djetty.port=8983 -DSTOP.PORT=7983 
-DSTOP.KEY=solrrocks -Duser.timezone=UTC -Djetty.home=/opt/solr-7.1.0/server 
-Dsolr.solr.home=/opt/solr-7.1.0/server/solr -Dsolr.data.home= 
-Dsolr.install.dir=/opt/solr-7.1.0 
-Dsolr.default.confdir=/opt/solr-7.1.0/server/solr/configsets/_default/conf 
-Xss256k -Dsolr.jetty.https.port=8983 -Dsolr.log.muteconsole 
-XX:OnOutOfMemoryError=/opt/solr-7.1.0/bin/oom_solr.sh 8983 
/opt/solr-7.1.0/server/logs -jar start.jar


Cache Configs are:









Find the attached thread dumps.


Please help!






Kumar Abhimeet | ICF Next
Senior Consultant
c: 080-46409406
icfolson.com
 | LinkedIn | 
Twitter
<>

Query regarding Solr Search

[Khare, Kushal (MIND)]

Hello People !
Hope you all are doing good !

Well, I am new to the solr server and want to use it for content search in one 
of my applications.
I have already been working upon it since quite a few days, and have the basics 
done.

The issue that I have is, I want my search to be restricted only upon the 
content and not the metadata. Currently, it return the document if the searched 
query is either in the content or the metadata.
So, please could anyone help me with this, as to how to search on these two 
fields independently.

Thanks in advance !
Regards,
Kushal Khare



The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any 
virus/trojan/worms/malicious code transmitted by this email. www.motherson.com

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Zheng Lin Edwin Yeo]

I am using Java version 1.8.0_221.

Ok, I will give it a try.

Regards,
Edwin

On Wed, 7 Aug 2019 at 14:52, Jan Høydahl  wrote:

> Which Java version are u using? Can you try to reproduce from scratch with
> a small cluster, no SSL etc, just solr 8.2 & zk 3.5.5 and create collection?
>
> Jan Høydahl
>
> > 7. aug. 2019 kl. 05:33 skrev Zheng Lin Edwin Yeo :
> >
> > Hi,
> >
> > From my Solr logs, any leads on why the collection creation failed, if
> the
> > issue is only a cosmetic issue?
> >
> > It can work correctly in this same new version of Solr when I use
> ZooKeeper
> > 3.4.14.
> >
> > Regards,
> > Edwin
> >
> >
> >> On Thu, 1 Aug 2019 at 18:05, Jörn Franke  wrote:
> >>
> >> For me:
> >> * ZK stand-alone mode - no issues
> >> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I
> >> see the same error message), but aside this Solr is working fine
> >>
> >>
> >>
> >>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo <
> edwinye...@gmail.com
> >>> :
> >>>
> >>> Hi Jörn,
> >>> Thank you for your reply.
> >>>
> >>> I have encountered problem when I tried to create a collection with
> this
> >>> new version of ZooKeeper. You can find my Solr log file here:
> >>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> >>>
> >>> Does it work perfectly at your side for creating collections and
> indexing
> >>> even when running ZooKeeper ensemble?
> >>>
> >>> Regards,
> >>> Edwin
> >>>
> >>>
>  On Thu, 1 Aug 2019 at 17:39, Jörn Franke 
> wrote:
> 
>  I confirm the issue.
> 
>  Interestingly it does not happen with ZK standalone, but only in a ZK
>  Ensemble.
> 
>  It seems to be mainly cosmetic in the admin UI because Solr appears to
>  function normally.
> 
> > Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo <
> >> edwinye...@gmail.com
> > :
> >
> > Yes. You can get my full solr.log from the link below. The error is
> >> there
> > when I tried to create collection1 (around line 170 to 300) .
> >
> > https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> >
> > Regards,
> > Edwin
> >
> >
> >> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>  wrote:
> >>
> >> Please look for the full log file solr.log in your Solr server, and
>  share
> >> it via some file sharing service or gist or similar for us to be
> able
> >> to
> >> decipher the collection create error.
> >>
> >> --
> >> Jan Høydahl, search solution architect
> >> Cominvent AS - www.cominvent.com
> >>
> >>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>  edwinye...@gmail.com
> >>> :
> >>>
> >>> Hi,
> >>>
> >>> Regarding the issue, I have tried to put the following in zoo.cfg
> >> under
> >>> ZooKeeper:
> >>> 4lw.commands.whitelist=mntr,conf,ruok
> >>>
> >>> But it is still showing this error.
> >>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>  zookeeper
> >>> configuration file."*
> >>>
> >>> As I am using SolrCloud, the collection config can still be loaded
> to
> >>> ZooKeeper as per normal. But if I tried to create a collection, I
> >> will
> >> get
> >>> the following error:
> >>>
> >>> {
> >>> "responseHeader":{
> >>> "status":400,
> >>> "QTime":686},
> >>> "failure":{
> >>> "192.168.1.2:8983
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at:http://192.168.1.2:8983/solr";,
> >>> "192.168.1.2:8984
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
> >>> "Operation create caused
> >>>
> >>
> 
> >>
> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> >>> Underlying core creation failed while creating collection:
>  collection1",
> >>> "exception":{f
> >>> "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>> "rspCode":400},
> >>> "error":{
> >>> "metadata":[
> >>>   "error-class","org.apache.solr.common.SolrException",
> >>>   "root-error-class","org.apache.solr.common.SolrException"],
> >>> "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>> "code":400}}
> >>>
> >>> Is there anything which I may have missed out?
> >>>
> >>> Regards,
> >>> Edwin
> >>>
> >>> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo <
>  edwinye...@gmail.com>
> >>> wrote:
> >>>
>  Hi,
> 
>  I am using the new Solr 8.2.0 with SolrCloud and external
> ZooKeeper
> >> 3.5.5.
> 
>  However, after adding in the line under zoo.cfg
>  *4lw.commands.whitelist=**
> 
>  I get the error under Cloud -> ZK Status in Sol