On 12/1/22 02:47, alessia.gagli...@qboxmail.it.INVALID wrote:
We have another solr (that handles less users) that had a high I/O
activity, which was reduced after increasing the physical memory from
24GB to 48GB. Could this be a scalable solution?
More memory not consumed by programs will ofte
Hello,
thank you for the answers. We reduced the heap size to 20GB and it has
made the situation better: it didn't stop, but the I/O activity was
still high.
We are a bit at a loss on what to monitor, maybe the garbage collector
activity?
I'm not aware of any particular planned recurrent
If it's always around the same time, one of the things to check is
cronjobs that run on the server and on all clients at that time. This
includes cronjobs that are scheduled to start at that time, and those that
start before it and might run long enough to reach a 'critical mass' by
that time.
Tho
Hello,
> Does anyone know what could be the cause of this behavior?
Not me, but if it usually occurs around midnight, i would enable INFO
logging and check for anomalies. Solr normally wouldn't trigger an action
at midnight. So i would look for an external trigger, sudden heavy indexing
with too
Hi,
Why the large Solr heap? What is happing around midnight? A nightly batch index?
Try lowering it from 30240m to e.g. 16g (or even lower) and see how it goes.
Jan
> 24. nov. 2022 kl. 12:21 skrev alessia.gagli...@qboxmail.it.invalid
> :
>
> Hi,
>
> we have a strange issue with solr: sometim
Hi,
we have a strange issue with solr: sometimes, usually everyday at around
midnight, solr becomes unreachable due to a high cpu load and high I/O
activity.
Our configurations are:
- Solr 7.7.3 on CentOS 7
- Dovecot 2.3.18 on CentOS 7
- /var/solr is around 250GB
- the Solr server has 4
