[ https://issues.apache.org/jira/browse/SOLR-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438709#comment-15438709 ]
Jan Høydahl commented on SOLR-9188: ----------------------------------- Trying to dig deeper: [~susheel2...@gmail.com] also reported on the mailing list but says that his cluster works well, except from the error logs. Are you sure there are no side effects? In SOLR-9257, [~MartinLoeper] says "This works well when there is no inter-node communication. As soon as I create a collection with 2 shards, I get the following exception for every access of the "/select" request handler. .... Error 401 Unauthorized request..." In SOLR-9257, [~shankarmc...@gmail.com] says that removing blockUnknown does not help. Can you confirm this? I rased the priority of this to Critical, please help shed some more light on this > BlockUnknown property makes inter-node communication impossible > --------------------------------------------------------------- > > Key: SOLR-9188 > URL: https://issues.apache.org/jira/browse/SOLR-9188 > Project: Solr > Issue Type: Bug > Components: SolrCloud > Affects Versions: 6.0 > Reporter: Piotr Tempes > Priority: Critical > Labels: BasicAuth, Security > Attachments: solr9188-errorlog.txt > > > When I setup my solr cloud without blockUnknown property it works as > expected. When I want to block non authenticated requests I get following > stacktrace during startup (see attached file). -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org