hi Solr Devs,
I need guidance on a problem I am having. We recently upgraded to
solr-8.11. We still use DIH to pull data from postgres DB.
We use solr in a standalone mode, with multiple cores, each core serving a
certain business unit.
When i try kicking off the dataimport handler i get the bel
Apache Solr's Docker images were updated some hours ago with a simple
remediation to avoid the Log4j 2 vulnerability[1] that many of you are
becoming aware of -- Log4j 2 CVE-2021-44228.
Just a "docker pull solr:tagVersionYouUse" (e.g. 8.11 or whatever) will
update it for you. The remediation in t
On 12/11/2021 7:49 PM, Surya R wrote:
Can anyone please let me know what this error is? Why is it referring to
update processor?
Thanks in advance for your help.
java.lang.NoSuchMethodError:
org.apache.solr.update.processor.TemplateUpdateProcessorFactory.replaceTokens(Ljava/lang/String;Lorg/apa
At a glance, a "NoSuchMethodError" strongly points to using incompatible
JARs. You say you are on Solr 8.11 but perhaps you have JARs for the DIH
of a previous version. They need to match. I checked right now that the
DIH in fact uses the method you point to, which lends credence to my theory.
Thanks Shawn,
I did as you suggested and replaced Xmx/Xms (I'm on FreeBSD by the way) with
SOLR_HEAP='16g' and I see it now uses that value instead for the running
process.
/usr/local/openjdk11/bin/java -server -Xms16g -Xmx16g -XX:+UseG1GC
-XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled
On 12/12/2021 4:40 PM, Scott wrote:
However, top still shows Solr using more than 16g . It started at 17g and has
been steadily growing, now it's at 23g and soon it will go into swap
PID USERNAMETHR PRI NICE SIZE RES SWAP STATEC TIME
WCPU COMMAND
57116 solr