see preformance


Good Day!!

Thank You for your patience and co-ordination.

From the below solr logs we suspect that Indexed data in Shard "CALSecurityLogs_shard8_replica2" might have got corrupted

2017-10-22 14:07:04,427 ERROR org.apache.solr.servlet.SolrDispatchFilter: null:org.apache.solr.common.SolrException: SolrCore 'CALSecurityLogs_shard8_replica2' is not available due to init failure: Error opening new searcher
        at org.apache.solr.core.CoreContainer.getCore(
        at org.apache.solr.servlet.SolrDispatchFilter.httpSolrCall(
        at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
        at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(
        at org.apache.solr.servlet.SolrHadoopAuthenticationFilter$2.doFilter(
        at org.apache.solr.servlet.SolrHadoopAuthenticationFilter.doFilter(
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(
        at org.apache.catalina.core.StandardWrapperValve.invoke(
        at org.apache.catalina.core.StandardContextValve.invoke(
        at org.apache.catalina.core.StandardHostValve.invoke(
        at org.apache.catalina.valves.ErrorReportValve.invoke(
        at org.apache.catalina.core.StandardEngineValve.invoke(
        at org.apache.catalina.connector.CoyoteAdapter.service(
        at org.apache.coyote.http11.Http11Processor.process(
Caused by: read past EOF:

In looking at your solr configs, solr.hdfs.blockcache.write.enabled is set to true, and that would definitely contribute to the issues we are seeing.

That is noted in the known release issues for Search

It is recommended to turn off blockcache.write

To do so, you would need to do the following (where collection_name is the name of your:

1. get the current instancedir from ZK:
solrctl instancedir --get CALSecurityLogs /path/to/collection

2. Change the solr.hdfs.blockcache.write.enabled to false in solrconfig.xml:
<bool name="solr.hdfs.blockcache.write.enabled">${solr.hdfs.blockcache.write.enabled:false}</bool>

3. upload your instancedir back to ZK after changing the value from true to false:
solrctl instancedir --update CALSecurityLogs /path/to/collection

4. Reload the solr collection:
solrctl collection --reload CALSecurityLogs

5. Verify through the Solr UI that the value is changed correctly:
Go to, select your core, and then select config and verify that solr.hdfs.blockcache.write.enabled is defaulted to false.

6. Restart the solr instances (if you need to do a rolling restart, you can restart each one separately)

Once that is done, it would be helpful to monitor the logs to confirm there are no further issues.

Enabling blockcache writing may result in unusable indexes

It is possible to create indexes with solr.hdfs.blockcache.write.enabled set to true. Such indexes may appear corrupt to readers, and reading these indexes may irrecoverably corrupt indexes. Blockcache writing is disabled by default.

Workaround: Do not enable blockcache writing.

Bug ID: CDH-17978
kb/solr/performance_tune.txt · Last modified: 2022/01/03 16:03 by
Back to top
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0