: Alright, i can now confirm the issue has been resolved by reducing precision.
: The garbage collector on nodes without reduced precision has a real hard time
: keeping up and clearly shows a very different graph of heap consumption.
:
: Consider using MINUTE, HOUR or DAY as precision in case
Well, it's quite hard to debug because the values listed on the stats page in
the fieldCache section don't make much sense. Reducing precision with
NOW/HOUR, however, does seem to make a difference.
It is hard (or impossible) to reproduce this is a test setup with the same
index but without
Alright, i can now confirm the issue has been resolved by reducing precision.
The garbage collector on nodes without reduced precision has a real hard time
keeping up and clearly shows a very different graph of heap consumption.
Consider using MINUTE, HOUR or DAY as precision in case you suffer
Hi,
In one of the environments i'm working on (4 Solr 1.4.1. nodes with
replication, 3+ million docs, ~5.5GB index size, high commit rate (~1-2min),
high query rate (~50q/s), high number of updates (~1000docs/commit)) the nodes
continuously run out of memory.
During development we frequently
