Thanks Erik!
I have created separate solr home directory for each solrclound node and
looks like now it's working fine.
GVK
On Mon, Oct 16, 2017 at 9:05 AM, Erick Erickson
wrote:
> bin/solr start -help
>
> will give you a lot of info. But yes, the -s option is what you should
> use. Here's on
bin/solr start -help
will give you a lot of info. But yes, the -s option is what you should
use. Here's one of my batch files I used to start various cloud
examples:
bin/solr start -c -z localhost:2181 -p 898 -s example/cloud/node1/solr
On Sun, Oct 15, 2017 at 11:48 PM, Gunalan V wrote:
> Thank
Thanks Erick,
I'm using the one VM where all SOLRCloud and Zookeeper nodes are running.
I have two solr nodes in solrcloud. Just wanted to check do I need to
create different solr home directory using -s param for each SOLR nodes ?
If yes kindly share me some documentation to configure separate
You might be hitting SOLR-11297, which is fixed in Solr 7.0.1. The
patch should back-port cleanly to 6x versions though.
Best,
Erick
On Thu, Oct 12, 2017 at 12:14 AM, Gunalan V wrote:
> Hello,
>
> I'm using SOLR 6.5.1 and I have 2 SOLR nodes in SOLRCloud and created
> collection using the below
Usually a message like "SolrCore 'corexxx' is not available due to init
failure" means that you had a syntax error in your schema.xml or
solrconfig.xml so that it could not be successfully processed by Solr (which
is done in the "init" method.)
Do a diff between your schema and config files be
I did more deep diving and found out the following exception while it tries
to replicate.
135531514-ERROR - 2014-03-07 23:08:35.454;
org.apache.solr.common.SolrException; SnapPull failed
:org.apache.lucene.store.AlreadyClosedException: Already closed
135531665- at
org.apache.solr.core.CachingDirec
Forgot to attach the log during the recovery failed
solr.log.129:1625677:ERROR - 2014-03-06 13:29:31.909;
org.apache.solr.common.SolrException; Error while trying to
recover:org.apache.solr.common.SolrException: Replication for recovery
failed.
solr.log.129-1625849- at
org.apache.solr.cloud.Recove
Hi
Why not copy the core directory instead of the data directory? The conf
directory is very small and that would ensure that you don't get schema
mismatch issues.
If you are stuck with copying the data directory, then I would replace the data
directory in the target core and reload that core,
Isn't it administratively easier with multiple cores instead of multiple
webapps??
Regards
Sujatha
On Tue, Mar 27, 2012 at 6:24 PM, Erick Erickson wrote:
> It might be administratively easier to have multiple webapps, but
> it shouldn't really matter as far as I know...
>
> Best
> Erick
>
> On
It might be administratively easier to have multiple webapps, but
it shouldn't really matter as far as I know...
Best
Erick
On Tue, Mar 27, 2012 at 12:22 AM, Sujatha Arun wrote:
> yes ,I must have mis-copied and yes, i do have the conf folder per core
> with schema etc ...
>
> Because of this is
yes ,I must have mis-copied and yes, i do have the conf folder per core
with schema etc ...
Because of this issue ,we have decided to have multiple webapps with about
50 cores per webapp ,instead of one singe webapp with all 200 cores ,would
this make better sense ?
what would be your suggestion
Shouldn't be. What do your log files say? You have to treat each
core as a separate index. In other words, you need to have a core#/conf
with the schema matching your core#/data/index directory etc.
I suspect you've simply mis-copied something.
Best
Erick
On Mon, Mar 26, 2012 at 8:27 AM, Sujatha
I was migrating to cores from webapp ,and I was copying a bunch of indexes
from webapps to respective cores ,when I restarted ,I had this issue where
the whole webapp with the cores would not startup and was getting index
corrupted message..
In this scenario or in a scenario where there is an issu
Index corruption is very rare, can you provide more details how you
got into that state?
Best
Erick
On Sun, Mar 25, 2012 at 1:22 PM, Sujatha Arun wrote:
> Hello,
>
> Suppose I have several cores in a single webapp ,I have issue with Index
> beong corrupted in one core ,or schema /solrconfig of
Your question can't be answered as asked, there are just too many
variables. Your best bet is to test and see.
Best
Erick
On Sun, Jan 29, 2012 at 6:37 AM, Ranveer Kumar wrote:
> How much query per second a single core can handle in this case..
>
> regards
>
> On Wed, Jan 25, 2012 at 9:49 AM, Suj
How much query per second a single core can handle in this case..
regards
On Wed, Jan 25, 2012 at 9:49 AM, Sujatha Arun wrote:
> Thanks Erick.
>
> Regards
> Sujatha
>
> On Mon, Jan 23, 2012 at 11:16 PM, Erick Erickson >wrote:
>
> > You can have a large number of cores, so people have multiple
Thanks Erick.
Regards
Sujatha
On Mon, Jan 23, 2012 at 11:16 PM, Erick Erickson wrote:
> You can have a large number of cores, some people have multiple
> hundreds. Having multiple cores is preferred over having
> multiple JVMs since it's more efficient at sharing system
> resources. If you're ru
You can have a large number of cores, some people have multiple
hundreds. Having multiple cores is preferred over having
multiple JVMs since it's more efficient at sharing system
resources. If you're running a 32 bit JVM, you are limited in
the amount of memory you can let the JVM use, so that's a
18 matches
Mail list logo
