I was copying the indexes from webapp to cores ,when this happened .It
could have been an error from my end ,but just worried that an issue with
one core would reflect on webapp .
Regards
Sujatha
On Mon, Apr 30, 2012 at 7:20 PM, Erick Erickson wrote:
> I'd get to the root of why indexes are cor
I'd get to the root of why indexes are corrupt! This should
be very unusual. If you're seeing this at all frequently,
it indicates something is very wrong and starting bunches
of JVMs up is a band-aid over a much more serious
problem.
Are you, by chance, doing a kill -9? or other hard-abort?
Best
Now the reason ,I have used different webapps instead of a single one for
the cores is ,while prototyping ,I discovered that ,when one of the cores
index is corrupt ,the entire webapp does not start up and the same must be
true of "too many open files" etc ,that is to say if there is an issue
with
Just my opinion, but I'm not sure I see the value in deploying the cores
to different webapps in a single container on a single machine to avoid
a single point of failure... You still have a single point of failure at
the process level down to the hardware, which when you think about it,
is mostly
Hello,
*Background* :For each of our customers, we create 3 solr webapps with
different search schema's,serving different search requirements and we
have about 70 customers.So we have about 210 webapps curently .
*Hardware*: Single Server , one JVM , Heap memory 19GB ,Total Ram :32GB ,
Permgen
