Hi Doug, Did you see any errors in the Solr server logs (of any of the 7 nodes) at the time? What makes you think GET vs POST is causing the problem? From a quick look at Nifi's PutSolrContentStream <https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-solr-bundle/nifi-solr-processors/src/main/java/org/apache/nifi/processors/solr/PutSolrContentStream.java> they use ContentStreamUpdateRequest <https://github.com/apache/solr/blob/main/solr/solrj/src/java/org/apache/solr/client/solrj/request/ContentStreamUpdateRequest.java> which is POST by default.
Matthias On Tue, May 2, 2023 at 4:53 PM Doug Whitfield <[email protected]> wrote: > Hi folks, > > Not sure if this is a better for the Nifi list, but going to start here > since the issue is in Solr. > > ENV: > Apache Solr 7.7 > OS Red Hat Enterprise Linux Server release 7.9 (Maipo). > > PROBLEM: > > We occasionally get request errors in the Apache Solr service, which > consists of 7 nodes. I am sharing a sample log below. Also, "start.jar" > errors are caught by the Dynatrace Agent. We are trying to find the root > cause (though we think at this point we have it). > > Error is this: org.apache.solr.client.solrj.SolrServerException: No live > SolrServers available to handle this request: > > As far as we can tell, the system self-heals (through a retry somewhere > presumably, but that’s not super important, I don’t think). Despite the > fact that this isn’t causing a true problem, we would like to clean this up > so we don’t have “false positives” in the error log. > > We believe this error is being caused by using a GET vs a POST. We have > seen this in a variety of forums. > > What is being used is > https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-solr-nar/1.11.4/org.apache.nifi.processors.solr.PutSolrContentStream/ > > I am not a Java developer, so perhaps this is a simple question, but what > I can’t tell is if there is an easy way to change the GET to a POST and > where I would do that. Would anybody be able to help with that aspect? Does > it sound like we are on the right track with the issue? > > Best Regards, > > Douglas Whitfield | Enterprise Architect > > > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
