I forgot to add: company from UK, something "log" related (please have a
look at recent LucidImagination -managed Solr Revolution conference blogs;
company provides "log analyzer" service; http://loggly.com/) they have
16,000 cores per Solr instance (multi-tenancy); of course they have at
least 100
I agree with Yonik of course;
But
You should see OOM errors in this case. In case of "virtualization"
however it is unpredictable and if JVM doesn't have few bytes to output
OOM into log file (because we are catching "throwable" and trying to
generate HTTP 500 instead !!! Freaky
EC2 7.5Gb (large CPU instance, $0.68/hour) sucks. Unpredictably, there are
errors such as
User time: 0 seconds
Kernel time: 0 seconds
Real time: 600 seconds
How can "clock time" be higher in such extent? Only if _another_ user used
600 seconds CPU: _virtualization_
My client have had constant p
What can I do temporarily in this situation? It seems like I must eventually
move to a distributed setup. I am sorting on dynamic float fields.
On Wed, Aug 17, 2011 at 3:01 PM, Yonik Seeley wrote:
> On Wed, Aug 17, 2011 at 5:56 PM, Jason Toy wrote:
> > I've only set set minimum memory and have
On Wed, Aug 17, 2011 at 5:56 PM, Jason Toy wrote:
> I've only set set minimum memory and have not set maximum memory. I'm doing
> more investigation and I see that I have 100+ dynamic fields for my
> documents, not the 10 fields I quoted earlier. I also sort against those
> dynamic fields often,
I've only set set minimum memory and have not set maximum memory. I'm doing
more investigation and I see that I have 100+ dynamic fields for my
documents, not the 10 fields I quoted earlier. I also sort against those
dynamic fields often, I'm reading that this potentially uses a lot of
memory.
Keep in mind that a commit warms up another searcher and potentially doubling
RAM consumption in the back ground due to cache warming queries being executed
(newSearcher event). Also, where is your Xmx switch? I don't know how your JVM
will behave if you set Xms > Xmx.
65m docs is quite a lot b
I've just checked my index size with and my data folder is 16GB. So if my
server only has 7.5 gb of ram, does that mean I can't reliably run solr on
this one box and its useless to optimize the box?
If so it look like its time to start using a cluster?
On Wed, Aug 17, 2011 at 2:28 PM, Herman Ki
While I can't be as specific as other here will be, we encountered the
same/similar problem. We simply loaded up our servers with 48GB and life is
good. I too would like to be a bit more proactive on the provisioning front
and hopefully someone will come along and help us out.
FWIW and I'm su
