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
Hello,
Suppose I have several cores in a single webapp ,I have issue with Index
beong corrupted in one core ,or schema /solrconfig of one core is not well
formed ,then entire webapp refused to load on server restart?
Why does this happen?
Regards
Sujatha
