Thank you Shawn - we have some WARN messages like :
DFSClient
Slow waitForAckedSeqno took 31066ms (threshold=30000ms)
and
DFSClient
Slow ReadProcessor read fields took 30737ms (threshold=30000ms); ack:
seqno: 1 reply: SUCCESS reply: SUCCESS reply: SUCCESS
downstreamAckTimeNanos: 30735948057,​ targets:
[DatanodeInfoWithStorage[172.16.100.223:50010,​DS-fc197ece-4c43-46a4-964e-9ecc8adcdcb1,​DISK],​
DatanodeInfoWithStorage[172.16.100.228:50010,​DS-fd9fe2ea-780b-490a-b9a7-ad54c994e307,​DISK],​
DatanodeInfoWithStorage[172.16.20.17:50010,​DS-63b38ca5-b674-4cdc-8102-f07a22709dc1,​DISK]]
I was getting the log ready for you, but it was overwritten in the
interim. If it happens again, I'll get the log file ready.
-Joe
On 7/12/2017 9:25 AM, Shawn Heisey wrote:
On 7/12/2017 7:14 AM, Joe Obernberger wrote:
Started up a 6.6.0 solr cloud instance running on 45 machines
yesterday using HDFS (managed schema in zookeeper) and began
indexing. This error occurred on several of the nodes:
<snip>
Caused by: org.apache.solr.common.SolrException: openNewSearcher
called on closed core
There's the important part of the error.
For some reason, which is not immediately clear from the information
provided, the core is closed. In that situation, Solr is not able to
open a new searcher, so this error happens. Do you have any other WARN
or ERROR messages in solr.log before this error? You might want to find
a way to share an entire logfile and provide a URL for accessing it.
Thanks,
Shawn
---
This email has been checked for viruses by AVG.
http://www.avg.com
