[
https://issues.apache.org/jira/browse/SOLR-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505466#comment-13505466
]
Markus Jelsma commented on SOLR-4116:
-------------------------------------
Restarting or stopping Tomcat shuts down CoreContainer and stops recovery, i
believe this is nice enough or isn't it? This error does not cause the core not
to come up.
{code}
2012-11-28 14:10:15,227 INFO [solr.core.CoreContainer] - [Thread-6] - :
Shutting down CoreContainer instance=1830423861
2012-11-28 14:10:15,227 WARN [solr.cloud.RecoveryStrategy] - [Thread-6] - :
Stopping recovery for zkNodeName=178.21.118.195:8080_solr_shard_fcore=shard_f
2012-11-28 14:10:15,227 WARN [solr.cloud.RecoveryStrategy] - [Thread-6] - :
Stopping recovery for zkNodeName=178.21.118.195:8080_solr_shard_gcore=shard_g
2012-11-28 14:10:15,227 INFO [solr.core.SolrCore] - [Thread-6] - : [shard_f]
CLOSING SolrCore org.apache.solr.core.SolrCore@513c952f
2012-11-28 14:10:15,230 INFO [solr.update.UpdateHandler] - [Thread-6] - :
closing DirectUpdateHandler2{commits=1,autocommit
maxTime=120000ms,autocommits=0,soft autocommit maxTime=10000ms,soft
autocommits=0,optimizes=0,rollbacks=0,expungeDeletes=0,docsPending=0,adds=0,deletesById=0,deletesByQuery=0,errors=0,cumulative_adds=0,cumulative_deletesById=0,cumulative_deletesByQuery=0,cumulative_errors=0}
2012-11-28 14:10:15,231 INFO [solr.core.SolrCore] - [Thread-6] - : Closing
SolrCoreState
2012-11-28 14:10:15,231 INFO [solr.update.DefaultSolrCoreState] - [Thread-6] -
: SolrCoreState ref count has reached 0 - closing IndexWriter
2012-11-28 14:10:15,231 INFO [solr.update.DefaultSolrCoreState] - [Thread-6] -
: closing IndexWriter with IndexWriterCloser
2012-11-28 14:10:15,234 INFO [solr.core.CachingDirectoryFactory] - [Thread-6] -
: Releasing directory:/opt/solr/cores/shard_f/data/index.20121128113300496
2012-11-28 14:10:15,235 INFO [solr.core.SolrCore] - [Thread-6] - : [shard_f]
Closing main searcher on request.
2012-11-28 14:10:15,244 INFO [solr.core.CachingDirectoryFactory] - [Thread-6] -
: Releasing directory:/opt/solr/cores/shard_f/data/index.20121128113300496
2012-11-28 14:10:15,244 INFO [solr.core.SolrCore] - [Thread-6] - : [shard_g]
CLOSING SolrCore org.apache.solr.core.SolrCore@24be0446
2012-11-28 14:10:15,248 INFO [solr.update.UpdateHandler] - [Thread-6] - :
closing DirectUpdateHandler2{commits=1,autocommit
maxTime=120000ms,autocommits=0,soft autocommit maxTime=10000ms,soft
autocommits=0,optimizes=0,rollbacks=0,expungeDeletes=0,docsPending=0,adds=0,deletesById=0,deletesByQuery=0,errors=0,cumulative_adds=0,cumulative_deletesById=0,cumulative_deletesByQuery=0,cumulative_errors=0}
2012-11-28 14:10:15,248 INFO [solr.core.SolrCore] - [Thread-6] - : Closing
SolrCoreState
2012-11-28 14:10:15,248 INFO [solr.update.DefaultSolrCoreState] - [Thread-6] -
: SolrCoreState ref count has reached 0 - closing IndexWriter
2012-11-28 14:10:15,248 INFO [solr.update.DefaultSolrCoreState] - [Thread-6] -
: closing IndexWriter with IndexWriterCloser
2012-11-28 14:10:15,250 INFO [solr.core.CachingDirectoryFactory] - [Thread-6] -
: Releasing directory:/opt/solr/cores/shard_g/data/index.20121128113035951
2012-11-28 14:10:15,250 INFO [solr.core.SolrCore] - [Thread-6] - : [shard_g]
Closing main searcher on request.
2012-11-28 14:10:15,256 INFO [solr.core.CachingDirectoryFactory] - [Thread-6] -
: Releasing directory:/opt/solr/cores/shard_g/data/index.20121128113035951
2012-11-28 14:10:15,281 INFO [apache.zookeeper.ZooKeeper] - [Thread-6] - :
Session: 0x13b4668803e000f closed
{code}
> Log Replay [recoveryExecutor-8-thread-1] - : java.io.EOFException
> -----------------------------------------------------------------
>
> Key: SOLR-4116
> URL: https://issues.apache.org/jira/browse/SOLR-4116
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.0
> Environment: 5.0.0.2012.11.28.10.42.06
> Debian Squeeze, Tomcat 6, Sun Java 6, 10 nodes, 10 shards, rep. factor 2.
> Reporter: Markus Jelsma
> Fix For: 5.0
>
>
> With SOLR-4032 fixed we see other issues when randomly taking down nodes
> (nicely via tomcat restart) while indexing a few million web pages from
> Hadoop. We do make sure that at least one node is up for a shard but due to
> recovery issues it may not be live.
> {code}
> 2012-11-28 11:32:33,086 WARN [solr.update.UpdateLog] -
> [recoveryExecutor-8-thread-1] - : Starting log replay
> tlog{file=/opt/solr/cores/openindex_e/data/tlog/tlog.0000000000000000028
> refcount=2} active=false starting pos=0
> 2012-11-28 11:32:41,873 ERROR [solr.update.UpdateLog] -
> [recoveryExecutor-8-thread-1] - : java.io.EOFException
> at
> org.apache.solr.common.util.FastInputStream.readFully(FastInputStream.java:151)
> at
> org.apache.solr.common.util.JavaBinCodec.readStr(JavaBinCodec.java:479)
> at
> org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:176)
> at
> org.apache.solr.common.util.JavaBinCodec.readSolrInputDocument(JavaBinCodec.java:374)
> at
> org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:225)
> at
> org.apache.solr.common.util.JavaBinCodec.readArray(JavaBinCodec.java:451)
> at
> org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:182)
> at
> org.apache.solr.update.TransactionLog$LogReader.next(TransactionLog.java:618)
> at
> org.apache.solr.update.UpdateLog$LogReplayer.doReplay(UpdateLog.java:1198)
> at
> org.apache.solr.update.UpdateLog$LogReplayer.run(UpdateLog.java:1143)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
