RE: Sitecore 9.3 / Solr 8.1.1 - Zookeeper Issue

2020-07-20 Thread Austin Kimmel
This error seems similar to what we are having:

http://mail-archives.apache.org/mod_mbox/lucene-dev/201907.mbox/%3ccapswd+oa5n3f2xqj0o58dqokpwudaefhynagoqg7rg3y8cu...@mail.gmail.com%3E


Austin Kimmel
Software Developer
Vail Resorts, Inc.
303-404-1922 
akim...@vailresorts.com

VAILRESORTS®
EXPERIENCE OF A LIFETIME


-Original Message-
From: Austin Kimmel 
Sent: Monday, July 20, 2020 9:10 AM
To: solr-user@lucene.apache.org
Cc: Simon Croak ; Shelby Busby 

Subject: RE: Sitecore 9.3 / Solr 8.1.1 - Zookeeper Issue

Hello,

I've been in contact with Sitecore Support, but they say that the issue is on 
the Solr side.  I see the errors when I am trying to rebuild the indexes.  The 
index is populated the first time and then each sequential time that I try to 
rebuild the index it or access it there is an error.  

This morning I was able to rebuild the index but saw the following error while 
it was processing in the log:

2020-07-20 14:36:56.273 ERROR 
(updateExecutor-5-thread-23-processing-x:pj4_sitecore_core_index_shard1_replica_n4
 r:core_node6 null n:10.5.64.40:8984_solr c:pj4_sitecore_core_index s:shard1) 
[c:pj4_sitecore_core_index s:shard1 r:core_node6 
x:pj4_sitecore_core_index_shard1_replica_n4] 
o.a.s.u.ErrorReportingConcurrentUpdateSolrClient Error when calling 
SolrCmdDistributor$Req: cmd=add{,id=(null)}; node=ForwardNode: 
https://10.5.64.41:8984/solr/pj4_sitecore_core_index_shard1_replica_n1/ to 
https://10.5.64.41:8984/solr/pj4_sitecore_core_index_shard1_replica_n1/ => 
java.io.IOException: java.io.IOException: Broken pipe
at 
org.eclipse.jetty.client.util.DeferredContentProvider.flush(DeferredContentProvider.java:193)
java.io.IOException: java.io.IOException: Broken pipe

That error is then the same error that I see after each following rebuild or 
when I try to access the index.

Here are the instructions that Sitecore provides with integrating Solr within 
their platform: 
https://doc.sitecore.com/developers/93/platform-administration-and-architecture/en/walkthrough--setting-up-solr.html

Thanks!

Austin Kimmel
Software Developer
Vail Resorts, Inc.
303-404-1922 
akim...@vailresorts.com

VAILRESORTS®
EXPERIENCE OF A LIFETIME

-Original Message-
From: matthew sporleder [mailto:msporle...@gmail.com] 
Sent: Monday, July 20, 2020 5:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Sitecore 9.3 / Solr 8.1.1 - Zookeeper Issue

ATTENTION: This eMail originated from outside of Vail Resorts and may or may 
not be legitimate. Although we do our best to screen phishing emails, please 
use extra caution before opening any attachments or clicking on any links 
unless you are absolutely sure the source of the email is trusted. If in doubt 
about the legitimacy of this email, please use the Report Phish button for 
validation.



FWIW the real error is msg":"SolrCore is loading which is bad if you are in the 
middle of indexing

What is happening on solr at this time?

> On Jul 20, 2020, at 4:46 AM, Charlie Hull  wrote:
>
> Hi Austin,
>
> Sitecore is a commercial product so your first port of call should be whoever 
> sold you or is supporting Sitecorea quick (and by no means deep) bit of 
> research shows this error may be generated by the Sitecore indexer process 
> calling Solr. We won't be able to see how it does that if it's closed source 
> code.
>
> Cheers
>
> Charlie
>
>> On 20/07/2020 04:53, Austin Kimmel wrote:
>> Hello,
>>
>> We are seeing the following errors with Sitecore 9.3 connecting to a Solr 
>> 8.1.1 cluster running on Zookeeper and haven't been able to resolve:
>>
>>
>> 2020-07-17 18:10:58.238 WARN  (zkCallback-8-thread-3) 
>> [c:pj4_sitecore_web_index s:shard1 r:core_node5 
>> x:pj4_sitecore_web_index_shard1_replica_n2] o.a.s.u.PeerSync PeerSync: 
>> core=pj4_sitecore_web_index_shard1_replica_n2 
>> url=https://10.5.64.40:8984/solr  got a 503 from 
>> https://10.5.64.41:8984/solr/pj4_sitecore_web_index_shard1_replica_n1/, 
>> counting as success => 
>> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
>> from server at 
>> https://10.5.64.41:8984/solr/pj4_sitecore_web_index_shard1_replica_n1: 
>> Expected mime type application/octet-stream but got application/json. {   
>> "error":{ "metadata":[   
>> "error-class","org.apache.solr.common.SolrException",   
>> "root-error-class","org.apache.solr.common.SolrException"], 
>> "msg":"SolrCore is loading", "code":503}}
>>
>> at 
>> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:613)
>>  org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
>> from server at 
>> https://10.5

RE: Sitecore 9.3 / Solr 8.1.1 - Zookeeper Issue

2020-07-20 Thread Austin Kimmel
Hello,

I've been in contact with Sitecore Support, but they say that the issue is on 
the Solr side.  I see the errors when I am trying to rebuild the indexes.  The 
index is populated the first time and then each sequential time that I try to 
rebuild the index it or access it there is an error.  

This morning I was able to rebuild the index but saw the following error while 
it was processing in the log:

2020-07-20 14:36:56.273 ERROR 
(updateExecutor-5-thread-23-processing-x:pj4_sitecore_core_index_shard1_replica_n4
 r:core_node6 null n:10.5.64.40:8984_solr c:pj4_sitecore_core_index s:shard1) 
[c:pj4_sitecore_core_index s:shard1 r:core_node6 
x:pj4_sitecore_core_index_shard1_replica_n4] 
o.a.s.u.ErrorReportingConcurrentUpdateSolrClient Error when calling 
SolrCmdDistributor$Req: cmd=add{,id=(null)}; node=ForwardNode: 
https://10.5.64.41:8984/solr/pj4_sitecore_core_index_shard1_replica_n1/ to 
https://10.5.64.41:8984/solr/pj4_sitecore_core_index_shard1_replica_n1/ => 
java.io.IOException: java.io.IOException: Broken pipe
at 
org.eclipse.jetty.client.util.DeferredContentProvider.flush(DeferredContentProvider.java:193)
java.io.IOException: java.io.IOException: Broken pipe

That error is then the same error that I see after each following rebuild or 
when I try to access the index.

Here are the instructions that Sitecore provides with integrating Solr within 
their platform: 
https://doc.sitecore.com/developers/93/platform-administration-and-architecture/en/walkthrough--setting-up-solr.html

Thanks!

Austin Kimmel
Software Developer
Vail Resorts, Inc.
303-404-1922 
akim...@vailresorts.com

VAILRESORTS®
EXPERIENCE OF A LIFETIME

-Original Message-
From: matthew sporleder [mailto:msporle...@gmail.com] 
Sent: Monday, July 20, 2020 5:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Sitecore 9.3 / Solr 8.1.1 - Zookeeper Issue

ATTENTION: This eMail originated from outside of Vail Resorts and may or may 
not be legitimate. Although we do our best to screen phishing emails, please 
use extra caution before opening any attachments or clicking on any links 
unless you are absolutely sure the source of the email is trusted. If in doubt 
about the legitimacy of this email, please use the Report Phish button for 
validation.



FWIW the real error is msg":"SolrCore is loading which is bad if you are in the 
middle of indexing

What is happening on solr at this time?

> On Jul 20, 2020, at 4:46 AM, Charlie Hull  wrote:
>
> Hi Austin,
>
> Sitecore is a commercial product so your first port of call should be whoever 
> sold you or is supporting Sitecorea quick (and by no means deep) bit of 
> research shows this error may be generated by the Sitecore indexer process 
> calling Solr. We won't be able to see how it does that if it's closed source 
> code.
>
> Cheers
>
> Charlie
>
>> On 20/07/2020 04:53, Austin Kimmel wrote:
>> Hello,
>>
>> We are seeing the following errors with Sitecore 9.3 connecting to a Solr 
>> 8.1.1 cluster running on Zookeeper and haven't been able to resolve:
>>
>>
>> 2020-07-17 18:10:58.238 WARN  (zkCallback-8-thread-3) 
>> [c:pj4_sitecore_web_index s:shard1 r:core_node5 
>> x:pj4_sitecore_web_index_shard1_replica_n2] o.a.s.u.PeerSync PeerSync: 
>> core=pj4_sitecore_web_index_shard1_replica_n2 
>> url=https://10.5.64.40:8984/solr  got a 503 from 
>> https://10.5.64.41:8984/solr/pj4_sitecore_web_index_shard1_replica_n1/, 
>> counting as success => 
>> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
>> from server at 
>> https://10.5.64.41:8984/solr/pj4_sitecore_web_index_shard1_replica_n1: 
>> Expected mime type application/octet-stream but got application/json. {   
>> "error":{ "metadata":[   
>> "error-class","org.apache.solr.common.SolrException",   
>> "root-error-class","org.apache.solr.common.SolrException"], 
>> "msg":"SolrCore is loading", "code":503}}
>>
>> at 
>> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:613)
>>  org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
>> from server at 
>> https://10.5.64.41:8984/solr/pj4_sitecore_web_index_shard1_replica_n1: 
>> Expected mime type application/octet-stream but got application/json. {   
>> "error":{ "metadata":[   
>> "error-class","org.apache.solr.common.SolrException",   
>> "root-error-class","org.apache.solr.common.SolrException"], 
>> "msg":"SolrCore is loading", "code":503}}
>>
>>
>> 2020-07-17 18:10:58.276 

Sitecore 9.3 / Solr 8.1.1 - Zookeeper Issue

2020-07-19 Thread Austin Kimmel
pe(ScopedHandler.java:201)
 at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
 at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)   
  at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
 at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
 at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) 
at 
org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
 at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) 
at org.eclipse.jetty.server.Server.handle(Server.java:502) at 
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364) at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) 
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
 at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) 
at 
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:411)
 at 
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:305) 
at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159)   
  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at 
org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
 at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
 at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
 at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
 at 
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
 at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
 at 
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) 
at java.base/java.lang.Thread.run(Thread.java:830) Caused by: 
org.apache.http.conn.HttpHostConnectException: Connect to 10.5.64.42:8984 
[/10.5.64.42] failed: Connection refused: no further information at 
org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:159)
 at 
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
 at 
org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:394)
 at 
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)  
   at 
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) 
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at 
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) 
at 
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
 at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
 at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
 at org.apache.solr.servlet.HttpSolrCall.remoteQuery(HttpSolrCall.java:664) 
... 41 more Caused by: java.net.ConnectException: Connection refused: no 
further information at java.base/sun.nio.ch.Net.pollConnect(Native Method)  
   at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:579) at 
java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:549)   
  at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597) at 
java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:339) at 
java.base/java.net.Socket.connect(Socket.java:603) at 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:339)
 at 
org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
 ... 51 more


2020-07-17 18:11:05.350 ERROR 
(updateExecutor-5-thread-7-processing-n:10.5.64.40:8984_solr 
x:pj4_sitecore_web_index_shard1_replica_n2 c:pj4_sitecore_web_index s:shard1 
r:core_node5) [c:pj4_sitecore_web_index s:shard1 r:core_node5 
x:pj4_sitecore_web_index_shard1_replica_n2] o.a.s.u.SolrCmdDistributor 
org.apache.solr.client.solrj.SolrServerException: IOException occured when 
talking to server at: null

at 
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:416)


Thanks!

Austin Kimmel
Software Developer
Vail Resorts, Inc.
303-404-1922
akim...@vailresorts.com<mailto:akim...@vailresorts.com>

VAILRESORTS(r)
EXPERIENCE OF A LIFETIME

The information contained in this message is confidential and intended only for 
the use of the individual or entity named above, and may be privileged. Any 
unauthorized review, use, disclosure, or distribution is prohibited. If you are 
not the intended recipient, please reply to the sender immediately, stating 
that you have received the message in error, then please delete this e-mail. 
Thank you.