Question about "No registered leader" error

2019-09-17 Thread Hongxu Ma
Hi all
I got an error when I was doing index operation:

"2019-09-18 02:35:44.427244 ... No registered leader was found after waiting 
for 4000ms , collection: foo slice: shard2"

Beside it, there is no other error in solr log.

Collection foo have 2 shards, then I check their jvm gc log:

  *   2019-09-18T02:34:08.252+: 150961.017: Total time for which 
application threads were stopped: 10.4617864 seconds, Stopping threads took: 
0.0005226 seconds

  *   2019-09-18T02:34:30.194+: 151014.108: Total time for which 
application threads were stopped: 44.4809415 seconds, Stopping threads took: 
0.0005976 seconds

I saw there are long gc pauses at the near timepoint.

My questions:

  *   Is this error possible caused by "long gc pause"? my solr 
zkClientTimeout=6
  *   If so, how can I prevent this error happen? My thoughts: using G1 
collector (as 
https://cwiki.apache.org/confluence/display/SOLR/ShawnHeisey#ShawnHeisey-GCTuningforSolr)
 or enlarge zkClientTimeout again, what's your idea?


Thanks.



Re: Why I receive permission denied when running as root

2019-09-17 Thread Erick Erickson
What it looks like is that execute permissions aren't set on bin/solr,
have you checked that?

Best,
Erick


On Tue, Sep 17, 2019 at 10:40 AM Shawn Heisey  wrote:
>
> On 9/16/2019 9:06 PM, Raymond Xie wrote:
> > [root@pocnnr1n1 solr]# bin/solr start
> > -bash: bin/solr: Permission denied
>
> The first thing I'd check for this is whether the bin/solr script has
> execute permission.  A lack of execute permissions can cause this problem.
>
> The first line of that script is this:
>
> #!/usr/bin/env bash
>
> Which means that /usr/bin/env must exist and also be executable, and
> that bash must be on the PATH that ends up being used by the env
> program, and bash must also be executable.  I think that problems with
> this *MIGHT* also cause the permission error.
>
> You could change the shebang to point directly at bash, something like this:
>
> #!/bin/bash
>
> Thanks,
> Shawn


Re: Unable to Create Collection on Solr Cloud 7.7.1

2019-09-17 Thread Shawn Heisey

On 9/17/2019 6:16 AM, iporritt wrote:

I am trying to create a collection on Solr Cloud. I have firstly uploaded
SolrConfig.xml and Schema.xml to Zookeeper.





HTTP ERROR 500
\nProblem accessing /solr/admin/cores. Reason:\nServer
Error
Caused by:
java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory\r\n\tat


Java could not find a Lucene class.

Something is wrong on your classpath.  Either the Solr install was 
modified in some way, possible by deleting one or more Lucene jars, or 
you have installed an additional copy of one or more Lucene jars 
somewhere else where Solr is loading them.  It could even be exactly the 
same 7.7.1 version as you are running, and could still cause this 
problem.  Jars like this that are already included in Solr should never 
be added to the classpath.


Thanks,
Shawn


Re: Why I receive permission denied when running as root

2019-09-17 Thread Shawn Heisey

On 9/16/2019 9:06 PM, Raymond Xie wrote:

[root@pocnnr1n1 solr]# bin/solr start
-bash: bin/solr: Permission denied


The first thing I'd check for this is whether the bin/solr script has 
execute permission.  A lack of execute permissions can cause this problem.


The first line of that script is this:

#!/usr/bin/env bash

Which means that /usr/bin/env must exist and also be executable, and 
that bash must be on the PATH that ends up being used by the env 
program, and bash must also be executable.  I think that problems with 
this *MIGHT* also cause the permission error.


You could change the shebang to point directly at bash, something like this:

#!/bin/bash

Thanks,
Shawn


Exception with cross-collection join query

2019-09-17 Thread Christof Lorenz
This has worked previously (solr 4.8) and does not work in solr 7.4. 
Fist query returns with proper result but index stops working from then on 
until restart.


13:43:02.573 [https-jsse-nio-8081-exec-6] ERROR org.apache.solr.core.SolrCore - 
Too many close [count:-1] on org.apache.solr.core.SolrCore@4233b99b. Please 
report this exception to solr-user@lucene.apache.org
13:43:02.574 [https-jsse-nio-8081-exec-6] ERROR org.apache.solr.core.SolrCore - 
Too many close [count:-2] on org.apache.solr.core.SolrCore@4233b99b. Please 
report this exception to solr-user@lucene.apache.org
13:43:02.574 [https-jsse-nio-8081-exec-6] ERROR org.apache.solr.core.SolrCore - 
Too many close [count:-3] on org.apache.solr.core.SolrCore@4233b99b. Please 
report this exception to solr-user@lucene.apache.org
13:43:02.574 [https-jsse-nio-8081-exec-6] ERROR org.apache.solr.core.SolrCore - 
Too many close [count:-4] on org.apache.solr.core.SolrCore@4233b99b. Please 
report this exception to solr-user@lucene.apache.org
13:43:02.574 [https-jsse-nio-8081-exec-6] ERROR org.apache.solr.core.SolrCore - 
Too many close [count:-5] on org.apache.solr.core.SolrCore@4233b99b. Please 
report this exception to solr-user@lucene.apache.org
13:43:20.407 [searcherExecutor-15-thread-1] ERROR 
org.apache.solr.search.FastLRUCache - Error during auto-warming of 
key:(+subject_std:misty* +subject_std:copeland*) (subject_std:misty* 
subject_std:copeland*)^1.0E-13 ("misty* copeland*")^1.0E9 (+from_std:misty* 
+from_std:copeland*) (from_std:misty* from_std:copeland*)^1.0E-13 ("misty* 
copeland*")^1.0E9 (+senderDisplay_std:misty* +senderDisplay_std:copeland*) 
(senderDisplay_std:misty* senderDisplay_std:copeland*)^1.0E-13 ("misty* 
copeland*")^1.0E9 (+sdomain_std:misty* +sdomain_std:copeland*) 
(sdomain_std:misty* sdomain_std:copeland*)^1.0E-13 ("misty* copeland*")^1.0E9 
(+recipients_std:misty* +recipients_std:copeland*) (recipients_std:misty* 
recipients_std:copeland*)^1.0E-13 ("misty* copeland*")^1.0E9 
(+rdomain_std:misty* +rdomain_std:copeland*) (rdomain_std:misty* 
rdomain_std:copeland*)^1.0E-13 ("misty* copeland*")^1.0E9 
(+categories_std:misty* +categories_std:copeland*) (categories_std:misty* 
categories_std:copeland*)^1.0E-13 ("misty* copeland*")^1.0E9 
(+filename_std:misty* +filename_std:copeland*) (filename_std:misty* 
filename_std:copeland*)^1.0E-13 ("misty* copeland*")^1.0E9 {!join from=id 
to=filedata_id fromIndex=retaincore_fd}+filedata_std:misty* 
+filedata_std:copeland* ({!join from=id to=filedata_id 
fromIndex=retaincore_fd}filedata_std:misty* filedata_std:copeland*)^1.0E-13 
({!join from=id to=filedata_id fromIndex=retaincore_fd}"misty* 
copeland*")^1.0E9:org.apache.solr.common.SolrException: openNewSearcher called 
on closed core
at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:2000)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:2246)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1983)
at 
org.apache.solr.search.JoinQuery$JoinQueryWeight.(JoinQParserPlugin.java:209)
at 
org.apache.solr.search.JoinQuery.createWeight(JoinQParserPlugin.java:169)
at 
org.apache.lucene.search.IndexSearcher.createWeight(IndexSearcher.java:743)
at org.apache.lucene.search.BooleanWeight.(BooleanWeight.java:54)
at 
org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:207)
at 
org.apache.lucene.search.IndexSearcher.createWeight(IndexSearcher.java:743)
at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:463)
at 
org.apache.solr.search.DocSetUtil.createDocSetGeneric(DocSetUtil.java:151)
at org.apache.solr.search.DocSetUtil.createDocSet(DocSetUtil.java:140)
at 
org.apache.solr.search.SolrIndexSearcher.getDocSetNC(SolrIndexSearcher.java:1196)
at 
org.apache.solr.search.SolrIndexSearcher.getDocSet(SolrIndexSearcher.java:818)
at 
org.apache.solr.search.SolrIndexSearcher.cacheDocSet(SolrIndexSearcher.java:759)
at 
org.apache.solr.search.SolrIndexSearcher$2.regenerateItem(SolrIndexSearcher.java:542)
at org.apache.solr.search.FastLRUCache.warm(FastLRUCache.java:193)
at 
org.apache.solr.search.SolrIndexSearcher.warm(SolrIndexSearcher.java:2169)
at 
org.apache.solr.core.SolrCore.lambda$getSearcher$16(SolrCore.java:2289)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:209)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)





Re: Is shard split operation multithreaded?

2019-09-17 Thread Antczak, Lukasz
Hi,
that's exactly what I needed to confirm. Thanks also for pointing to Solr
code.
Regards
Łukasz

On Tue, Sep 17, 2019 at 10:23 AM Andrzej Białecki  wrote:

> If I understand your question correctly .. it’s single-threaded with
> regard to a specific shard - but you can run multiple shard splitting
> operations in parallel IFF they affect different shards (or different
> collections).
>
> See SplitShardCmd for the details of locking and how the new sub-shards
> are initialised and replicated. Part of the shard splitting always runs
> asynchronously, namely the part where the new sub-shards are replicated and
> recovered, and only once this part is done the new sub-shards become active
> and the old parent shard becomes inactive. You can find this code in
> ReplicaMutator.checkAndCompleteShardSplit.
>
> > On 17 Sep 2019, at 09:51, Antczak, Lukasz 
> wrote:
> >
> > Hello,
> > I have short question to Solr experts.
> > Is shard split operation single- or multi- threaded?
> >
> > Regards
> > Łukasz Antczak
> >
> > --
> > *Łukasz Antczak*
> > Senior IT Professional
> > GS Data Frontiers Team 
> >
> > *Planned absences:*
> > *11th August - 18th August*
> > *26th August - 1st September*
> > *Roche Polska Sp. z o.o.*
> > ADMD Group Services - Business Intelligence Team
> > HQ: ul. Domaniewska 39B, 02-672 Warszawa
> > Office: ul. Abpa Baraniaka 88D, 61-131 Poznań
> >
> > Mobile: +48 519 515 010
> > mailto: lukasz.antc...@roche.com
> >
> > *Informacja o poufności: *Treść tej wiadomości zawiera informacje
> > przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej
> > adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o
> > tym nadawcy oraz trwałe jej usunięcie. Wszelkie nieuprawnione
> > wykorzystanie informacji zawartych w tej wiadomości jest zabronione.
> >
> > *Confidentiality Note:* This message is intended only for the use of the
> > named recipient(s) and may contain confidential and/or proprietary
> > information. If you are not the intended recipient, please contact the
> > sender and delete this message. Any unauthorized use of the information
> > contained in this message is prohibited.
>
>

-- 
*Łukasz Antczak*
Senior IT Professional
GS Data Frontiers Team 

*Planned absences:*
*11th August - 18th August*
*26th August - 1st September*
*Roche Polska Sp. z o.o.*
ADMD Group Services - Business Intelligence Team
HQ: ul. Domaniewska 39B, 02-672 Warszawa
Office: ul. Abpa Baraniaka 88D, 61-131 Poznań

Mobile: +48 519 515 010
mailto: lukasz.antc...@roche.com

*Informacja o poufności: *Treść tej wiadomości zawiera informacje
przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej
adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o
tym nadawcy oraz trwałe jej usunięcie. Wszelkie nieuprawnione
wykorzystanie informacji zawartych w tej wiadomości jest zabronione.

*Confidentiality Note:* This message is intended only for the use of the
named recipient(s) and may contain confidential and/or proprietary
information. If you are not the intended recipient, please contact the
sender and delete this message. Any unauthorized use of the information
contained in this message is prohibited.


Re: Why I receive permission denied when running as root

2019-09-17 Thread Raymond Xie
Thank you Paras for your reply, yes I downloaded src, after re-download the
binary, it is working as expected here.

**
*Sincerely yours,*


*Raymond*


On Tue, Sep 17, 2019 at 9:26 AM Paras Lehana 
wrote:

> Hi Raymond,
>
> ERROR: start.jar file not found in /opt/solr-8.2.0/solr/server!
>>
>
> You had probably downloaded the source version. *Download the binary one*
> (TGZ
> 
> or ZIP
> ).
> Yes, it does mean that the package is incomplete.
>
> On Tue, 17 Sep 2019 at 18:40, Raymond Xie  wrote:
>
>> Thank you Paras:
>>
>> If I am already user of root, and still run sudo? no, it doesn't work:
>> [root@pocnnr1n1 solr]# sudo bin/solr start -force
>> sudo: bin/solr: command not found
>>
>> [root@pocnnr1n1 solr]# ls -l bin/solr
>> -rw-r--r-- 1 root root 80630 Jul 19 09:09 bin/solr
>>
>> So, I followed your suggestion and added +x, now run the command again:
>> [root@pocnnr1n1 solr]# bin/solr start
>> *** [WARN] *** Your open file limit is currently 1024.
>>  It should be set to 65000 to avoid operational disruption.
>>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
>> false in your profile or solr.in.sh
>> *** [WARN] ***  Your Max Processes Limit is currently 63397.
>>  It should be set to 65000 to avoid operational disruption.
>>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
>> false in your profile or solr.in.sh
>> WARNING: Starting Solr as the root user is a security risk and not
>> considered best practice. Exiting.
>>  Please consult the Reference Guide. To override this check,
>> start with argument '-force'
>>
>> alright, I'll add the -force option:
>> [root@pocnnr1n1 solr]# bin/solr start -force
>> *** [WARN] *** Your open file limit is currently 1024.
>>  It should be set to 65000 to avoid operational disruption.
>>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
>> false in your profile or solr.in.sh
>> *** [WARN] ***  Your Max Processes Limit is currently 63397.
>>  It should be set to 65000 to avoid operational disruption.
>>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
>> false in your profile or solr.in.sh
>>
>> ERROR: start.jar file not found in /opt/solr-8.2.0/solr/server!
>> Please check your -d parameter to set the correct Solr server directory.
>>
>> BUT: the folder server is there, and no start.jar
>>
>> [root@pocnnr1n1 solr]# ls /opt/solr-8.2.0/solr
>> bin  common-build.xml  licensesserver  webapp
>> bin-test contrib   LICENSE.txt site
>> build.xmlcore  LUCENE_CHANGES.txt  solrj
>> CHANGES.txt  docs  NOTICE.txt  solr-ref-guide
>> cloud-devexample   README.txt  test-framework
>>
>> [root@pocnnr1n1 server]# ll
>> total 16
>> drwxr-xr-x 2 root root6 Jul 19 09:09 solr-webapp
>> drwxr-xr-x 3 root root   27 Jul 19 09:09 scripts
>> -rw-r--r-- 1 root root 3959 Jul 19 09:09 README.txt
>> -rw-r--r-- 1 root root 5740 Jul 19 09:09 ivy.xml
>> -rw-r--r-- 1 root root 2214 Jul 19 09:09 build.xml
>> drwxr-xr-x 2 root root  135 Sep 16 21:13 etc
>> drwxr-xr-x 2 root root   36 Sep 16 21:13 contexts
>> drwxr-xr-x 2 root root   82 Sep 16 21:13 resources
>> drwxr-xr-x 2 root root   90 Sep 16 21:13 modules
>> drwxr-xr-x 3 root root   73 Sep 16 21:13 solr
>>
>> *So this seems to be something missing from the solr package?*
>>
>> *Thank you.*
>>
>> **
>> *Sincerely yours,*
>>
>>
>> *Raymond*
>>
>>
>> On Tue, Sep 17, 2019 at 8:42 AM Paras Lehana 
>> wrote:
>>
>>> Hey Raymond,
>>>
>>>
>>> bin/solr start -force
>>>
>>>
>>> I know this could be useless, but did you try the following (notice the
>>> sudo)?
>>>
>>> *sudo* bin/solr start -force
>>>
>>>
>>> Also, I suggest you to review permission of solr file by:
>>>
>>> ls -l bin/solr
>>>
>>>
>>> If you don't see required executable permissions, you can provide root
>>> user the permission to execute the file by:
>>>
>>> *chmod +x bin/solr*
>>>
>>>
>>> Hope this helps.
>>>
>>> On Tue, 17 Sep 2019 at 18:03, Raymond Xie  wrote:
>>>
 Thank you.

 As I suspected, this is something else. It prompts me the same error
 here:
 [root@pocnnr1n1 solr]# bin/solr start -force
 -bash: bin/solr: Permission denied
 [root@pocnnr1n1 solr]#

 It is not a good practice to use root directly, however, using root
 should not have permission error. This is odd.


 **
 *Sincerely yours,*


 *Raymond*


 On Tue, Sep 17, 2019 at 12:49 AM Paras Lehana <
 paras.leh...@indiamart.com> wrote:

> Hi Raymond,
>
> It's not recommended to run solr as root (security reasons
> 

Re: Why I receive permission denied when running as root

2019-09-17 Thread Paras Lehana
Hi Raymond,

ERROR: start.jar file not found in /opt/solr-8.2.0/solr/server!
>

You had probably downloaded the source version. *Download the binary one* (
TGZ 
or ZIP
).
Yes, it does mean that the package is incomplete.

On Tue, 17 Sep 2019 at 18:40, Raymond Xie  wrote:

> Thank you Paras:
>
> If I am already user of root, and still run sudo? no, it doesn't work:
> [root@pocnnr1n1 solr]# sudo bin/solr start -force
> sudo: bin/solr: command not found
>
> [root@pocnnr1n1 solr]# ls -l bin/solr
> -rw-r--r-- 1 root root 80630 Jul 19 09:09 bin/solr
>
> So, I followed your suggestion and added +x, now run the command again:
> [root@pocnnr1n1 solr]# bin/solr start
> *** [WARN] *** Your open file limit is currently 1024.
>  It should be set to 65000 to avoid operational disruption.
>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
> false in your profile or solr.in.sh
> *** [WARN] ***  Your Max Processes Limit is currently 63397.
>  It should be set to 65000 to avoid operational disruption.
>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
> false in your profile or solr.in.sh
> WARNING: Starting Solr as the root user is a security risk and not
> considered best practice. Exiting.
>  Please consult the Reference Guide. To override this check, start
> with argument '-force'
>
> alright, I'll add the -force option:
> [root@pocnnr1n1 solr]# bin/solr start -force
> *** [WARN] *** Your open file limit is currently 1024.
>  It should be set to 65000 to avoid operational disruption.
>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
> false in your profile or solr.in.sh
> *** [WARN] ***  Your Max Processes Limit is currently 63397.
>  It should be set to 65000 to avoid operational disruption.
>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to
> false in your profile or solr.in.sh
>
> ERROR: start.jar file not found in /opt/solr-8.2.0/solr/server!
> Please check your -d parameter to set the correct Solr server directory.
>
> BUT: the folder server is there, and no start.jar
>
> [root@pocnnr1n1 solr]# ls /opt/solr-8.2.0/solr
> bin  common-build.xml  licensesserver  webapp
> bin-test contrib   LICENSE.txt site
> build.xmlcore  LUCENE_CHANGES.txt  solrj
> CHANGES.txt  docs  NOTICE.txt  solr-ref-guide
> cloud-devexample   README.txt  test-framework
>
> [root@pocnnr1n1 server]# ll
> total 16
> drwxr-xr-x 2 root root6 Jul 19 09:09 solr-webapp
> drwxr-xr-x 3 root root   27 Jul 19 09:09 scripts
> -rw-r--r-- 1 root root 3959 Jul 19 09:09 README.txt
> -rw-r--r-- 1 root root 5740 Jul 19 09:09 ivy.xml
> -rw-r--r-- 1 root root 2214 Jul 19 09:09 build.xml
> drwxr-xr-x 2 root root  135 Sep 16 21:13 etc
> drwxr-xr-x 2 root root   36 Sep 16 21:13 contexts
> drwxr-xr-x 2 root root   82 Sep 16 21:13 resources
> drwxr-xr-x 2 root root   90 Sep 16 21:13 modules
> drwxr-xr-x 3 root root   73 Sep 16 21:13 solr
>
> *So this seems to be something missing from the solr package?*
>
> *Thank you.*
>
> **
> *Sincerely yours,*
>
>
> *Raymond*
>
>
> On Tue, Sep 17, 2019 at 8:42 AM Paras Lehana 
> wrote:
>
>> Hey Raymond,
>>
>>
>> bin/solr start -force
>>
>>
>> I know this could be useless, but did you try the following (notice the
>> sudo)?
>>
>> *sudo* bin/solr start -force
>>
>>
>> Also, I suggest you to review permission of solr file by:
>>
>> ls -l bin/solr
>>
>>
>> If you don't see required executable permissions, you can provide root
>> user the permission to execute the file by:
>>
>> *chmod +x bin/solr*
>>
>>
>> Hope this helps.
>>
>> On Tue, 17 Sep 2019 at 18:03, Raymond Xie  wrote:
>>
>>> Thank you.
>>>
>>> As I suspected, this is something else. It prompts me the same error
>>> here:
>>> [root@pocnnr1n1 solr]# bin/solr start -force
>>> -bash: bin/solr: Permission denied
>>> [root@pocnnr1n1 solr]#
>>>
>>> It is not a good practice to use root directly, however, using root
>>> should not have permission error. This is odd.
>>>
>>>
>>> **
>>> *Sincerely yours,*
>>>
>>>
>>> *Raymond*
>>>
>>>
>>> On Tue, Sep 17, 2019 at 12:49 AM Paras Lehana <
>>> paras.leh...@indiamart.com> wrote:
>>>
 Hi Raymond,

 It's not recommended to run solr as root (security reasons
 ).
 Nevertheless, in order to answer your question, try this command:

 *sudo bin/solr start -force*


 From Solr Control Script Reference
 
 :

 If attempting to start Solr as the root user, the script will exit with

Re: Why I receive permission denied when running as root

2019-09-17 Thread Raymond Xie
Thank you Paras:

If I am already user of root, and still run sudo? no, it doesn't work:
[root@pocnnr1n1 solr]# sudo bin/solr start -force
sudo: bin/solr: command not found

[root@pocnnr1n1 solr]# ls -l bin/solr
-rw-r--r-- 1 root root 80630 Jul 19 09:09 bin/solr

So, I followed your suggestion and added +x, now run the command again:
[root@pocnnr1n1 solr]# bin/solr start
*** [WARN] *** Your open file limit is currently 1024.
 It should be set to 65000 to avoid operational disruption.
 If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
in your profile or solr.in.sh
*** [WARN] ***  Your Max Processes Limit is currently 63397.
 It should be set to 65000 to avoid operational disruption.
 If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
in your profile or solr.in.sh
WARNING: Starting Solr as the root user is a security risk and not
considered best practice. Exiting.
 Please consult the Reference Guide. To override this check, start
with argument '-force'

alright, I'll add the -force option:
[root@pocnnr1n1 solr]# bin/solr start -force
*** [WARN] *** Your open file limit is currently 1024.
 It should be set to 65000 to avoid operational disruption.
 If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
in your profile or solr.in.sh
*** [WARN] ***  Your Max Processes Limit is currently 63397.
 It should be set to 65000 to avoid operational disruption.
 If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
in your profile or solr.in.sh

ERROR: start.jar file not found in /opt/solr-8.2.0/solr/server!
Please check your -d parameter to set the correct Solr server directory.

BUT: the folder server is there, and no start.jar

[root@pocnnr1n1 solr]# ls /opt/solr-8.2.0/solr
bin  common-build.xml  licensesserver  webapp
bin-test contrib   LICENSE.txt site
build.xmlcore  LUCENE_CHANGES.txt  solrj
CHANGES.txt  docs  NOTICE.txt  solr-ref-guide
cloud-devexample   README.txt  test-framework

[root@pocnnr1n1 server]# ll
total 16
drwxr-xr-x 2 root root6 Jul 19 09:09 solr-webapp
drwxr-xr-x 3 root root   27 Jul 19 09:09 scripts
-rw-r--r-- 1 root root 3959 Jul 19 09:09 README.txt
-rw-r--r-- 1 root root 5740 Jul 19 09:09 ivy.xml
-rw-r--r-- 1 root root 2214 Jul 19 09:09 build.xml
drwxr-xr-x 2 root root  135 Sep 16 21:13 etc
drwxr-xr-x 2 root root   36 Sep 16 21:13 contexts
drwxr-xr-x 2 root root   82 Sep 16 21:13 resources
drwxr-xr-x 2 root root   90 Sep 16 21:13 modules
drwxr-xr-x 3 root root   73 Sep 16 21:13 solr

*So this seems to be something missing from the solr package?*

*Thank you.*

**
*Sincerely yours,*


*Raymond*


On Tue, Sep 17, 2019 at 8:42 AM Paras Lehana 
wrote:

> Hey Raymond,
>
>
> bin/solr start -force
>
>
> I know this could be useless, but did you try the following (notice the
> sudo)?
>
> *sudo* bin/solr start -force
>
>
> Also, I suggest you to review permission of solr file by:
>
> ls -l bin/solr
>
>
> If you don't see required executable permissions, you can provide root
> user the permission to execute the file by:
>
> *chmod +x bin/solr*
>
>
> Hope this helps.
>
> On Tue, 17 Sep 2019 at 18:03, Raymond Xie  wrote:
>
>> Thank you.
>>
>> As I suspected, this is something else. It prompts me the same error here:
>> [root@pocnnr1n1 solr]# bin/solr start -force
>> -bash: bin/solr: Permission denied
>> [root@pocnnr1n1 solr]#
>>
>> It is not a good practice to use root directly, however, using root
>> should not have permission error. This is odd.
>>
>>
>> **
>> *Sincerely yours,*
>>
>>
>> *Raymond*
>>
>>
>> On Tue, Sep 17, 2019 at 12:49 AM Paras Lehana 
>> wrote:
>>
>>> Hi Raymond,
>>>
>>> It's not recommended to run solr as root (security reasons
>>> ).
>>> Nevertheless, in order to answer your question, try this command:
>>>
>>> *sudo bin/solr start -force*
>>>
>>>
>>> From Solr Control Script Reference
>>> 
>>> :
>>>
>>> If attempting to start Solr as the root user, the script will exit with
 a warning that running Solr as "root" can cause problems. It is possible to
 override this warning with the -force parameter.
>>>
>>>
>>> PS: I suggest you to go through *Service Installation Script *in Taking
>>> Solr to Production
>>>  
>>> that
>>> describes the ideal Solr setup. A must read!
>>>
>>> Hope I helped.
>>>
>>>
>>> On Tue, 17 Sep 2019 at 08:37, Raymond Xie  wrote:
>>>
 [root@pocnnr1n1 solr-8.2.0]# ll
 total 88
 -rw-r--r--  1 root root  4023 Jul 19 09:09 README.md
 -rw-r--r--  1 root root 32153 Jul 19 09:09 build.xml
 

Re: Why I receive permission denied when running as root

2019-09-17 Thread Paras Lehana
Hey Raymond,


bin/solr start -force


I know this could be useless, but did you try the following (notice the
sudo)?

*sudo* bin/solr start -force


Also, I suggest you to review permission of solr file by:

ls -l bin/solr


If you don't see required executable permissions, you can provide root user
the permission to execute the file by:

*chmod +x bin/solr*


Hope this helps.

On Tue, 17 Sep 2019 at 18:03, Raymond Xie  wrote:

> Thank you.
>
> As I suspected, this is something else. It prompts me the same error here:
> [root@pocnnr1n1 solr]# bin/solr start -force
> -bash: bin/solr: Permission denied
> [root@pocnnr1n1 solr]#
>
> It is not a good practice to use root directly, however, using root should
> not have permission error. This is odd.
>
>
> **
> *Sincerely yours,*
>
>
> *Raymond*
>
>
> On Tue, Sep 17, 2019 at 12:49 AM Paras Lehana 
> wrote:
>
>> Hi Raymond,
>>
>> It's not recommended to run solr as root (security reasons
>> ).
>> Nevertheless, in order to answer your question, try this command:
>>
>> *sudo bin/solr start -force*
>>
>>
>> From Solr Control Script Reference
>> 
>> :
>>
>> If attempting to start Solr as the root user, the script will exit with a
>>> warning that running Solr as "root" can cause problems. It is possible to
>>> override this warning with the -force parameter.
>>
>>
>> PS: I suggest you to go through *Service Installation Script *in Taking
>> Solr to Production
>>  
>> that
>> describes the ideal Solr setup. A must read!
>>
>> Hope I helped.
>>
>>
>> On Tue, 17 Sep 2019 at 08:37, Raymond Xie  wrote:
>>
>>> [root@pocnnr1n1 solr-8.2.0]# ll
>>> total 88
>>> -rw-r--r--  1 root root  4023 Jul 19 09:09 README.md
>>> -rw-r--r--  1 root root 32153 Jul 19 09:09 build.xml
>>> -rw-r--r--  1 root root 27717 Jul 19 09:09 NOTICE.txt
>>> -rw-r--r--  1 root root 12646 Jul 19 09:09 LICENSE.txt
>>> drwxr-xr-x 10 root root   174 Sep 16 21:13 dev-tools
>>> drwxr-xr-x 30 root root  4096 Sep 16 21:13 lucene
>>> drwxr-xr-x 16 root root  4096 Sep 16 21:13 solr
>>>
>>> [root@pocnnr1n1 solr]# bin/solr start
>>> -bash: bin/solr: Permission denied
>>>
>>> Can anyone please help me to sort it out?
>>>
>>> Thank you. Regards.
>>> **
>>> *Sincerely yours,*
>>>
>>>
>>> *Raymond*
>>>
>>
>>
>> --
>> --
>> Regards,
>>
>> *Paras Lehana* [65871]
>> Software Programmer, Auto-Suggest,
>> IndiaMART Intermesh Ltd.
>>
>> 8th Floor, Tower A, Advant-Navis Business Park, Sector 142,
>> Noida, UP, IN - 201303
>>
>> Mob.: +91-9560911996
>> Work: 01203916600 | Extn:  *8173*
>>
>> IMPORTANT:
>> NEVER share your IndiaMART OTP/ Password with anyone.
>>
>

-- 
-- 
Regards,

*Paras Lehana* [65871]
Software Programmer, Auto-Suggest,
IndiaMART Intermesh Ltd.

8th Floor, Tower A, Advant-Navis Business Park, Sector 142,
Noida, UP, IN - 201303

Mob.: +91-9560911996
Work: 01203916600 | Extn:  *8173*

-- 
IMPORTANT: 
NEVER share your IndiaMART OTP/ Password with anyone.


Re: Why I receive permission denied when running as root

2019-09-17 Thread Jost Baron
Maybe the execute permission is missing on bin/solr?

Try `chmod a+x bin/solr` (this gives *all* users execute permission for
bin/solr).

On 17.09.19 14:33, Raymond Xie wrote:
> Thank you.
> 
> As I suspected, this is something else. It prompts me the same error here:
> [root@pocnnr1n1 solr]# bin/solr start -force
> -bash: bin/solr: Permission denied
> [root@pocnnr1n1 solr]#
> 
> It is not a good practice to use root directly, however, using root should
> not have permission error. This is odd.
> 
> 
> **
> *Sincerely yours,*
> 
> 
> *Raymond*
> 
> 
> On Tue, Sep 17, 2019 at 12:49 AM Paras Lehana 
> wrote:
> 
>> Hi Raymond,
>>
>> It's not recommended to run solr as root (security reasons
>> ).
>> Nevertheless, in order to answer your question, try this command:
>>
>> *sudo bin/solr start -force*
>>
>>
>> From Solr Control Script Reference
>> 
>> :
>>
>> If attempting to start Solr as the root user, the script will exit with a
>>> warning that running Solr as "root" can cause problems. It is possible to
>>> override this warning with the -force parameter.
>>
>>
>> PS: I suggest you to go through *Service Installation Script *in Taking
>> Solr to Production
>>  
>> that
>> describes the ideal Solr setup. A must read!
>>
>> Hope I helped.
>>
>>
>> On Tue, 17 Sep 2019 at 08:37, Raymond Xie  wrote:
>>
>>> [root@pocnnr1n1 solr-8.2.0]# ll
>>> total 88
>>> -rw-r--r--  1 root root  4023 Jul 19 09:09 README.md
>>> -rw-r--r--  1 root root 32153 Jul 19 09:09 build.xml
>>> -rw-r--r--  1 root root 27717 Jul 19 09:09 NOTICE.txt
>>> -rw-r--r--  1 root root 12646 Jul 19 09:09 LICENSE.txt
>>> drwxr-xr-x 10 root root   174 Sep 16 21:13 dev-tools
>>> drwxr-xr-x 30 root root  4096 Sep 16 21:13 lucene
>>> drwxr-xr-x 16 root root  4096 Sep 16 21:13 solr
>>>
>>> [root@pocnnr1n1 solr]# bin/solr start
>>> -bash: bin/solr: Permission denied
>>>
>>> Can anyone please help me to sort it out?
>>>
>>> Thank you. Regards.
>>> **
>>> *Sincerely yours,*
>>>
>>>
>>> *Raymond*
>>>
>>
>>
>> --
>> --
>> Regards,
>>
>> *Paras Lehana* [65871]
>> Software Programmer, Auto-Suggest,
>> IndiaMART Intermesh Ltd.
>>
>> 8th Floor, Tower A, Advant-Navis Business Park, Sector 142,
>> Noida, UP, IN - 201303
>>
>> Mob.: +91-9560911996
>> Work: 01203916600 | Extn:  *8173*
>>
>> IMPORTANT:
>> NEVER share your IndiaMART OTP/ Password with anyone.
>>
> 


Re: Why I receive permission denied when running as root

2019-09-17 Thread Raymond Xie
Thank you.

As I suspected, this is something else. It prompts me the same error here:
[root@pocnnr1n1 solr]# bin/solr start -force
-bash: bin/solr: Permission denied
[root@pocnnr1n1 solr]#

It is not a good practice to use root directly, however, using root should
not have permission error. This is odd.


**
*Sincerely yours,*


*Raymond*


On Tue, Sep 17, 2019 at 12:49 AM Paras Lehana 
wrote:

> Hi Raymond,
>
> It's not recommended to run solr as root (security reasons
> ).
> Nevertheless, in order to answer your question, try this command:
>
> *sudo bin/solr start -force*
>
>
> From Solr Control Script Reference
> 
> :
>
> If attempting to start Solr as the root user, the script will exit with a
>> warning that running Solr as "root" can cause problems. It is possible to
>> override this warning with the -force parameter.
>
>
> PS: I suggest you to go through *Service Installation Script *in Taking
> Solr to Production
>  that
> describes the ideal Solr setup. A must read!
>
> Hope I helped.
>
>
> On Tue, 17 Sep 2019 at 08:37, Raymond Xie  wrote:
>
>> [root@pocnnr1n1 solr-8.2.0]# ll
>> total 88
>> -rw-r--r--  1 root root  4023 Jul 19 09:09 README.md
>> -rw-r--r--  1 root root 32153 Jul 19 09:09 build.xml
>> -rw-r--r--  1 root root 27717 Jul 19 09:09 NOTICE.txt
>> -rw-r--r--  1 root root 12646 Jul 19 09:09 LICENSE.txt
>> drwxr-xr-x 10 root root   174 Sep 16 21:13 dev-tools
>> drwxr-xr-x 30 root root  4096 Sep 16 21:13 lucene
>> drwxr-xr-x 16 root root  4096 Sep 16 21:13 solr
>>
>> [root@pocnnr1n1 solr]# bin/solr start
>> -bash: bin/solr: Permission denied
>>
>> Can anyone please help me to sort it out?
>>
>> Thank you. Regards.
>> **
>> *Sincerely yours,*
>>
>>
>> *Raymond*
>>
>
>
> --
> --
> Regards,
>
> *Paras Lehana* [65871]
> Software Programmer, Auto-Suggest,
> IndiaMART Intermesh Ltd.
>
> 8th Floor, Tower A, Advant-Navis Business Park, Sector 142,
> Noida, UP, IN - 201303
>
> Mob.: +91-9560911996
> Work: 01203916600 | Extn:  *8173*
>
> IMPORTANT:
> NEVER share your IndiaMART OTP/ Password with anyone.
>


Unable to Create Collection on Solr Cloud 7.7.1

2019-09-17 Thread iporritt
I am trying to create a collection on Solr Cloud. I have firstly uploaded
SolrConfig.xml and Schema.xml to Zookeeper. The SolrConfig.XML is as
follows:






  

  
  7.7.1

  

  

  
  

  
  

  
  

  
  
  
  
  

  
  ${solr.data.dir:}


  
  

  
  

  
  


















${solr.lock.type:native}













  


  
  
  
  
  
  

  
  



  ${solr.ulog.dir:}
  ${solr.ulog.numVersionBuckets:65536}




  ${solr.autoCommit.maxTime:15000}
  false





  ${solr.autoSoftCommit.maxTime:-1}




  

  
  

  
  


${solr.max.booleanClauses:1024}























true





20


200




  

  


  

  



false

  


  
  








  

  
  
  


  explicit
  10
  
  








  

  
  

  explicit
  json
  true

  


  
  

  explicit

  

  

  _text_

  

  
  

  true
  ignored_
  _text_

  

  

  
  

text_general





  default
  _text_
  solr.DirectSolrSpellChecker
  
  internal
  
  0.5
  
  2
  
  1
  
  5
  
  4
  
  0.01
  




  

  
  

  
  default
  on
  true
  10
  5
  5
  true
  true
  10
  5


  spellcheck

  

  
  

  
  

  true


  tvComponent

  

  

  
  

  
  

  true
  false


  terms

  


  
  

string
  

  
  

  explicit


  elevator

  

  
  

  
  
  

  100

  

  
  

  
  70
  
  0.5
  
  [-\w ,/\n\]{20,200}

  

  
  

  
  

  

  
  

  
  

  
  

  
  

  
  

  

  
  

  
  

  

  

  10
  .,!? 

  

  

  
  WORD
  
  
  en
  US

  

  

  

  
  
  
  
[^\w-\.]
_
  
  
  
  
  

  -MM-dd'T'HH:mm:ss.SSSZ
  -MM-dd'T'HH:mm:ss,SSSZ
  -MM-dd'T'HH:mm:ss.SSS
  -MM-dd'T'HH:mm:ss,SSS
  -MM-dd'T'HH:mm:ssZ
  -MM-dd'T'HH:mm:ss
  -MM-dd'T'HH:mmZ
  -MM-dd'T'HH:mm
  -MM-dd HH:mm:ss.SSSZ
  -MM-dd HH:mm:ss,SSSZ
  -MM-dd HH:mm:ss.SSS
  -MM-dd HH:mm:ss,SSS
  -MM-dd HH:mm:ssZ
  -MM-dd HH:mm:ss
  -MM-dd HH:mmZ
  -MM-dd HH:mm
  -MM-dd

  
  

  java.lang.String
  text_general
  
*_str
256
  
  
  true


  java.lang.Boolean
  booleans


  java.util.Date
  pdates


  java.lang.Long
  java.lang.Integer
  plongs


  java.lang.Number
  pdoubles

  

  
  



  

  
  

  
  

  
  

  
  
  

  

text/plain; charset=UTF-8
  

  
  
${velocity.template.base.dir:}
${velocity.solr.resource.loader.enabled:true}
${velocity.params.resource.loader.enabled:false}
  

  
  
5
  

  
  
  

  
  
  


  
  




The only difference between this one and the _default one is the
SchemaFactory class at the bottom.

When trying to create a collection via Web Request
http://localhost:8983/solr/admin/collections?action=CREATE=test=test=1=1
I get the following error output:

{
  "responseHeader":{
"status":0,
"QTime":1863},
  "failure":{
   
"192.168.56.1:8983_solr":"org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error
from server at http://192.168.56.1:8983/solr: Expected mime type
application/octet-stream but got text/html. \n\n\nError 500 Server
Error\n\n
HTTP ERROR 500
\nProblem accessing /solr/admin/cores. Reason:\nServer
Error
Caused by:
java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory\r\n\tat
java.lang.ClassLoader.defineClass1(Native Method)\r\n\tat
java.lang.ClassLoader.defineClass(ClassLoader.java:763)\r\n\tat
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)\r\n\tat
java.net.URLClassLoader.defineClass(URLClassLoader.java:468)\r\n\tat
java.net.URLClassLoader.access$100(URLClassLoader.java:74)\r\n\tat
java.net.URLClassLoader$1.run(URLClassLoader.java:369)\r\n\tat
java.net.URLClassLoader$1.run(URLClassLoader.java:363)\r\n\tat
java.security.AccessController.doPrivileged(Native Method)\r\n\tat

Re: HDFS Shard Split

2019-09-17 Thread Andrzej Białecki
SplitShardCmd assumes that its main phase (when the Lucene index is being 
split) always executes on the local file system of the shard leader, and indeed 
the ShardSplitCmd.checkDiskSpace() checks the local file system’s free disk 
space - even though in reality in your case the actual data is written to the 
HDFS Directory so it (almost) doesn’t affect the local FS…

Please file a JIRA request to improve this. For now you simply have to make 
sure that you have at least 2x the index size of free disk space available on 
the shard leader.

> On 16 Sep 2019, at 18:15, Joe Obernberger  
> wrote:
> 
> Hi All - added a couple more solr nodes to an existing solr cloud cluster 
> where the index is in HDFS.  When I try to a split a shard, I get an error 
> saying there is not enough disk space.  It looks like it is looking on the 
> local file system, and not in HDFS.
> 
> "Operation splitshard casued 
> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>  not enough free disk space to perform index split on node
> 
> -Joe
> 



Re: Is shard split operation multithreaded?

2019-09-17 Thread Andrzej Białecki
If I understand your question correctly .. it’s single-threaded with regard to 
a specific shard - but you can run multiple shard splitting operations in 
parallel IFF they affect different shards (or different collections).

See SplitShardCmd for the details of locking and how the new sub-shards are 
initialised and replicated. Part of the shard splitting always runs 
asynchronously, namely the part where the new sub-shards are replicated and 
recovered, and only once this part is done the new sub-shards become active and 
the old parent shard becomes inactive. You can find this code in 
ReplicaMutator.checkAndCompleteShardSplit.

> On 17 Sep 2019, at 09:51, Antczak, Lukasz  wrote:
> 
> Hello,
> I have short question to Solr experts.
> Is shard split operation single- or multi- threaded?
> 
> Regards
> Łukasz Antczak
> 
> -- 
> *Łukasz Antczak*
> Senior IT Professional
> GS Data Frontiers Team 
> 
> *Planned absences:*
> *11th August - 18th August*
> *26th August - 1st September*
> *Roche Polska Sp. z o.o.*
> ADMD Group Services - Business Intelligence Team
> HQ: ul. Domaniewska 39B, 02-672 Warszawa
> Office: ul. Abpa Baraniaka 88D, 61-131 Poznań
> 
> Mobile: +48 519 515 010
> mailto: lukasz.antc...@roche.com
> 
> *Informacja o poufności: *Treść tej wiadomości zawiera informacje
> przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej
> adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o
> tym nadawcy oraz trwałe jej usunięcie. Wszelkie nieuprawnione
> wykorzystanie informacji zawartych w tej wiadomości jest zabronione.
> 
> *Confidentiality Note:* This message is intended only for the use of the
> named recipient(s) and may contain confidential and/or proprietary
> information. If you are not the intended recipient, please contact the
> sender and delete this message. Any unauthorized use of the information
> contained in this message is prohibited.



Is shard split operation multithreaded?

2019-09-17 Thread Antczak, Lukasz
Hello,
I have short question to Solr experts.
Is shard split operation single- or multi- threaded?

Regards
Łukasz Antczak

-- 
*Łukasz Antczak*
Senior IT Professional
GS Data Frontiers Team 

*Planned absences:*
*11th August - 18th August*
*26th August - 1st September*
*Roche Polska Sp. z o.o.*
ADMD Group Services - Business Intelligence Team
HQ: ul. Domaniewska 39B, 02-672 Warszawa
Office: ul. Abpa Baraniaka 88D, 61-131 Poznań

Mobile: +48 519 515 010
mailto: lukasz.antc...@roche.com

*Informacja o poufności: *Treść tej wiadomości zawiera informacje
przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej
adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o
tym nadawcy oraz trwałe jej usunięcie. Wszelkie nieuprawnione
wykorzystanie informacji zawartych w tej wiadomości jest zabronione.

*Confidentiality Note:* This message is intended only for the use of the
named recipient(s) and may contain confidential and/or proprietary
information. If you are not the intended recipient, please contact the
sender and delete this message. Any unauthorized use of the information
contained in this message is prohibited.