Hi,
I have the following document which fails to get indexed.
{
"asset_id":"add-ons:576deefef7453a9189aa039b66500eb2",
"reference_url":"modeling-a-high-speed-backplane-part-3-4-port-s-parameters-to-differential-tdr-and-tdt.html"}
I am not sure what is so special about the content in the
Hi,
Just summarizing:
I've experimented using different sized of filtercache and documentcache,
after removing any maxRamMB. Now the heap seems to behave as expected,
that is, it grows, then GC (not full one) kicks in multiple times and keep
the used heap under control. eventually full GC may kic
Rather than getting rid of the terminology, we should get rid of the
standalone mode Solr altogether. I totally understand that SolrCloud is
broken in many ways today, but we should attempt to fix it and have it as
the only mode in Solr.
On Wed, 24 Jun, 2020, 8:17 pm Mike Drob, wrote:
> Brend,
>
For people who is also looking for the solution - you can append
"node=node_name" in metrics request to get specific data of node.
If anyone know how to get the data if all the nodes together, please kindly
share, thanks.
Regards,
Chien
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-U
Hi Reinaldo,
Glad that helped. I've had several sleepless nights with Solr clusters
failing spectacularly in production due to that but I still cannot say that
the problem is completely away.
Did you check in the heap dump if you have cache memory leaks as described
in https://issues.apache.org/
