[
https://issues.apache.org/jira/browse/SOLR-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903604#comment-13903604
]
Mark Miller commented on SOLR-5735:
-----------------------------------
It *looks* like this is happening when we commit simply to force open a new
searcher after peer syncing in recovery. So what happened? Not sure yet ... we
opened on an index that was screwed up due to some replication fail?
We could catch everything except out of memory exceptions and if any of this
peer sync part fails, try replication? But I still don't know for sure why the
above happens. In the past it may have been hidden by the fact that we caught
assertions and so we would have retried rather than bailing out of the recovery
thread.
> ChaosMonkey test timeouts.
> --------------------------
>
> Key: SOLR-5735
> URL: https://issues.apache.org/jira/browse/SOLR-5735
> Project: Solr
> Issue Type: Task
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.7, 5.0
>
>
> This started showing up in jenkins runs a while back.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
