Internode communication failed when enable basic authentication Solr 6.1.0
Hi Team,
Basic Authentication is enabled on Solr cloud and node1 is running on one
machine and node2 is runnin on second machine, zookeeper installed on
second machine. Getting unathorized error when enable basic auth, error
mostly occure when machine trying access machine 2 solr and also while
starting solr also i can see the error message.
It would be grateful if you help me to resole the issue. I saw some jira
ticket stating that some internode communication issue and got fixed in
solr 6, but I am using solr 6 only and also getting isssue, Even-though am
login admin user on solr UI, sometime getting Error 401 Unauthorized
request mostly request go to node1 to node2.
[c:adm s:shard2 r:core_node2 x:adm_shard2_replica2 ]
o.a.s.h.RequestHandlerBase
org.apache.solr.client.solrj.impl.HttpSolrClient$Re
moteSolrException:
Error from server at http://172.16.7.58:8983/solr/adm_shard2_ replica1:
Expected mime type application/octet-stream but got text/html.
Error 401 Unauthorized request, Response code: 401
HTTP ERROR 401
Problem accessing /solr/adm_shard2_replica1/select. Reason:
* Unauthorized request, Response code: 401*
*Below code define in security.json*
-bash-3.2# curl --user solr:SolrRocks
http://localhost:8983/solr/admin/authorization
{
"responseHeader":{
"status":0,
"QTime":0},
"authorization.enabled":true,
"authorization":{
"class":"solr.RuleBasedAuthorizationPlugin",
"user-role":{"solr":"admin"},
"permissions":[{
"name":"security-edit",
"role":"admin",
"index":1},
{
"name":"read",
"role":"admin",
"index":2},
{
"name":"collection-admin-read ",
"role":"admin",
"index":3}],
"":{"v":50}}}
Thanks,
Shankar.
Contact: 91+9894546732
Re: Internode communication failed when enable basic authentication Solr 6.1.0
Hi,
Sorry for the late reply, Yes above issue is related to
https://issues.apache.org/jira/browse/SOLR-9188 . Could you please let me
know the workaround for this.
Thanks,
Shankar.
On Fri, Jul 8, 2016 at 7:13 PM, Aleš Gregor wrote:
> Hello,
>
> could this be related to https://issues.apache.org/jira/browse/SOLR-9188 ?
>
> Ales Gregor
>
>
>
> 2016-06-24 15:15 GMT+02:00 Shankar Ramalingam :
>
> > Hi Team,
> >
> > Basic Authentication is enabled on Solr cloud and node1 is running on one
> > machine and node2 is runnin on second machine, zookeeper installed on
> > second machine. Getting unathorized error when enable basic auth, error
> > mostly occure when machine trying access machine 2 solr and also while
> > starting solr also i can see the error message.
> >
> >
> > It would be grateful if you help me to resole the issue. I saw some jira
> > ticket stating that some internode communication issue and got fixed in
> > solr 6, but I am using solr 6 only and also getting isssue, Even-though
> am
> > login admin user on solr UI, sometime getting Error 401 Unauthorized
> > request mostly request go to node1 to node2.
> >
> >
> >
> > [c:adm s:shard2 r:core_node2 x:adm_shard2_replica2 ]
> > o.a.s.h.RequestHandlerBase
> > org.apache.solr.client.solrj.impl.HttpSolrClient$Re
> > moteSolrException:
> > Error from server at http://172.16.7.58:8983/solr/adm_shard2_ replica1:
> > Expected mime type application/octet-stream but got text/html.
> >
> >
> > Error 401 Unauthorized request, Response code: 401
> >
> > HTTP ERROR 401
> > Problem accessing /solr/adm_shard2_replica1/select. Reason:
> >* Unauthorized request, Response code: 401*
> >
> >
> >
> >
> >
> > *Below code define in security.json*
> >
> > -bash-3.2# curl --user solr:SolrRocks
> > http://localhost:8983/solr/admin/authorization
> > {
> > "responseHeader":{
> > "status":0,
> > "QTime":0},
> > "authorization.enabled":true,
> > "authorization":{
> > "class":"solr.RuleBasedAuthorizationPlugin",
> > "user-role":{"solr":"admin"},
> > "permissions":[{
> > "name":"security-edit",
> > "role":"admin",
> > "index":1},
> > {
> > "name":"read",
> > "role":"admin",
> > "index":2},
> > {
> > "name":"collection-admin-read ",
> > "role":"admin",
> > "index":3}],
> > "":{"v":50}}}
> >
> >
> >
> > Thanks,
> > Shankar.
> > Contact: 91+9894546732
> >
>
Re: Index fetch failed
Please remove my email id from this list. On Tue, 3 Sep, 2019, 11:06 AM Akreeti Agarwal, wrote: > Hello, > > Please help me with the solution for below error. > > Memory details of slave server: > total used free sharedbuffers cached > Mem: 15947 15460487 62144 6007 > -/+ buffers/cache: 9308 6639 > Swap:0 0 0 > > > Thanks & Regards, > Akreeti Agarwal > > -Original Message- > From: Akreeti Agarwal > Sent: Wednesday, August 28, 2019 2:45 PM > To: solr-user@lucene.apache.org > Subject: RE: Index fetch failed > > Yes I am using solr-5.5.5. > This error is intermittent. I don't think there must be any issue with > master connection limits. This error is accompanied by this on master side: > > ERROR (qtp1450821318-60072) [ x:sitecore_web_index] > o.a.s.h.ReplicationHandler Unable to get file names for indexCommit > generation: 1558637 > java.nio.file.NoSuchFileException: > /solrm-efs/solr-m/server/solr/sitecore_web_index/data/index/_12i9p_1.liv >at > sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) >at > sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) >at > sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) >at > sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55) >at > sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144) >at > sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99) >at java.nio.file.Files.readAttributes(Files.java:1737) >at java.nio.file.Files.size(Files.java:2332) >at > org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:210) >at > org.apache.lucene.store.NRTCachingDirectory.fileLength(NRTCachingDirectory.java:124) >at > org.apache.solr.handler.ReplicationHandler.getFileList(ReplicationHandler.java:563) >at > org.apache.solr.handler.ReplicationHandler.handleRequestBody(ReplicationHandler.java:253) >at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155) >at org.apache.solr.core.SolrCore.execute(SolrCore.java:2102) >at > org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654) >at > org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460) >at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257) >at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208) >at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) >at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) >at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) >at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) >at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) >at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) >at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) >at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) >at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) >at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) >at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) >at org.eclipse.jetty.server.Server.handle(Server.java:499) >at > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) >at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) >at org.eclipse.jetty.io > .AbstractConnection$2.run(AbstractConnection.java:540) >at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) >at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) >at java.lang.Thread.run(Thread.java:748) > > Thanks & Regards, > Akreeti Agarwal > > -Original Message- > From: Atita Arora > Sent: Wednesday, August 28, 2019 2:23 PM > To: solr-user@lucene.apache.org > Subject: Re: Index fetch failed > > This looks like ample memory to
Re: Atomic indexing as default indexing mode in Solr
Please remove my email id from this list. On Thu, 5 Sep, 2019, 5:55 AM Erick Erickson, wrote: > Because atomic updates require special preparation, specifically all > original fields must be stored which is not a requirement and is, in fact, > an anti-pattern in large installations. > > Best, > Erick > > > On Sep 4, 2019, at 7:51 PM, Arnold Bronley > wrote: > > > > Why atomic indexing is not the default mode of indexing in Solr? That way > > the ownership model of the content changes from document level to field > > level for clients. Multiple clients can participate in the contribution > > process of the same Solr document without overwriting each other. > >
