Closed pavanKumar2211 closed 1 year ago
So the issue is that Solr 9.x has the Java Security Manager enabled by default, while Solr 8.x did not.
It looks like the Newrelic jar you are using requires permissions that do not come out-of-the-box with Solr, which is unsurprising. You can provide a custom envVar SOLR_SECURITY_MANAGER_ENABLED=false
to disable the Java security manager.
Unfortunately, I don't think there is a very good way to upload a custom security manager via the operator, unless you want to make your own Solr image that pulls the official image, and overrides the security manager config.
So the issue is that Solr 9.x has the Java Security Manager enabled by default, while Solr 8.x did not.
It looks like the Newrelic jar you are using requires permissions that do not come out-of-the-box with Solr, which is unsurprising. You can provide a custom envVar
SOLR_SECURITY_MANAGER_ENABLED=false
to disable the Java security manager.Unfortunately, I don't think there is a very good way to upload a custom security manager via the operator, unless you want to make your own Solr image that pulls the official image, and overrides the security manager config.
Thanks a lot! I added the envVar in Dockerfile provided by solr and pushed into my repository and used it. It worked.
You can also provide custom envVars through SolrCloud.spec.customSolrKubeOptions.podOptions.envVars
. That's probably an easier solution than creating a custom image đŸ™‚
We are deploying apache solr operator https://github.com/apache/solr-operator in AWS EKS 1.23 via helm Currently we are using: Apache Solr operator Image: v0.5.1 Apache Solrcloud Image: v8.8
Now we are upgrading to 9.2 which is compatible with operator 0.5.1
We are installing newrelic agent by downloading newrelic.jar file from https://download.newrelic.com/newrelic/java-agent/newrelic-agent/current/newrelic-java.zip
Under solrOptions to execute newrelic jar we are giving javaOpts="-javaagent:/path/to/newrelic.jar" for solr 8.8. Now we are upgrading to 9.2 which is compatible with operator 0.5.1. With the solrOptions in solr v8.8 the apache-solrcloud pods are running fine and solr is being traced over newrelic but using same configuration for solr v9.2 apache-solrcloud pods are failing to start.
Attaching complete error stacktrace
We are getting below error:
2023-05-26 10:06:43.194 INFO (main) [ ] o.e.j.s.RequestLogWriter Opened /var/solr/logs/2023_05_26.request.log 2023-05-26 10:06:43.215 INFO (main) [ ] o.e.j.s.AbstractConnector Started ServerConnector@2017f6e6{HTTP/1.1, (http/1.1, h2c)}{0.0.0.0:8983} 2023-05-26 10:06:43.219 INFO (main) [ ] o.e.j.s.Server Started Server@3db6dd52{STARTING}[10.0.13,sto=0] @5552ms 2023-05-26 10:06:56.685 WARN (qtp718057154-60) [ ] o.e.j.i.ManagedSelector Could not accept java.nio.channels.SocketChannel[closed]: java.lang.VerifyError: Bad type on operand stack