Eventually we managed to figure out what happened. we deploy our cluster on
RedHat OpenShift Container Platform 4.7, and apparently our specific minor had
a known issue with creating containers that can run more than 1024 threads.
We solved the issue by asking our providers to implement the relev
Our system resources are:
OS (as a docker) has 4cpu and 32GB RAM, and we gave Solr 12GB java heap.
If I understand you correctly this situation is not like what you had @Gaikwad,
correct? (We should also have enough physical memory for all of our containers
without getting into a problem).
Sent
we've tried to check if that's the problem but we couldn't really understand
how to check that...
what were the parameters you changed specifically? (we work with linux)
thanks,
123456780sss
‐‐‐ Original Message ‐‐‐
On Saturday, January 22nd, 2022 at 7:34 PM, Rajendra Gaikwad
wrote:
Another reason could be insufficient memory available with the OS.
I faced a similar issue in the past, after releasing some amount of memory
it works.
e.g Machine/Server has 6 GB total memory, Java process allocated 5.4 GB and
OS left with 600MB, It was causing the same issue(unable to create nati
On 1/20/22 5:54 AM, 123456780sss wrote:
However, we've checked the nproc and nofile in our cluster and right now they
are set to 4096 each, unlike the 1024 that was theorized. We will probably try
to raise it to 8192 anyway, but we're not sure that the impact will be as great
as expected initi
Thanks for the advice, it looks like a promising direction.
However, we've checked the nproc and nofile in our cluster and right now they
are set to 4096 each, unlike the 1024 that was theorized. We will probably try
to raise it to 8192 anyway, but we're not sure that the impact will be as great
On 1/13/22 8:24 AM, Shawn Heisey wrote:
You need to allow the user that is running Solr to have more
processes/threads and more open files. On Linux you can add lines
like the following to /etc/security/limits.conf:|
solr hard nofile 8192||
solr soft nofile 8192||
solr hard nproc 8192||
solr
On 1/10/22 1:49 AM, 123456780sss wrote:
Recenently, we start getting errors of "out of memory, cannot create native
thread",
Even a small install can easily start enough threads to cause problems
for an OS that is configured with defaults. Most operating systems
default to a limit of 1024.
Thanks for the reply!
Just to make sure I understand correctly:
I send the request to "https:///solr//stream" "expr=search( my open a thread, and sends a request to
a replica in each shard.
Each replica that receive a request execute a query on , and then return
the result to the , which coll
CloudSolrStream uses a thread pool to create a SolrStream to a replica on
each shard. Each thread exits after it returns one record, but the initial
search on each shard completes within a thread. After one record is
returned a single thread is used to merge the results from each shard. But
the ini
Sorry I forgot to add - we are using Solr 6.5.1
Sent with [ProtonMail](https://protonmail.com/) Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, January 10th, 2022 at 10:49, 123456780sss
<123456780...@protonmail.com> wrote:
> I am using Solr for some time now, and I encounter a problem
I am using Solr for some time now, and I encounter a problem with our threads.
I am running Solr cloud, having 4 collections in total, and overall about 600
shards (each with 2 replicas) between all of the collections.
Recenently, we start getting errors of "out of memory, cannot create native
12 matches
Mail list logo
