[
https://issues.apache.org/jira/browse/SOLR-9189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317500#comment-15317500
]
Hoss Man commented on SOLR-9189:
--------------------------------
yeah ... i think the evidence is pretty strong that this issue was caused by
something related to the ZkStateReader changes [~romseygeek] was working on in
SOLR-9181+SOLR-9140...
sarowe's 6.x jenkins job just finished build#1207 -- the first build after
4e3884bec7c386fe718abc423b2381b68aaf1a97 landed on branch_6x -- and it only
took 12 minutes (this in spite of the fact that i made no SSL randomization
suppression related changes to branch_6x as part of this issue -- that was just
to master)
http://jenkins.sarowe.net/job/Lucene-Solr-tests-6.x/1207/
Just to be safe, i'll leave 59b4fc0bb0105ec25285f763fde86739433a38b1 on master
until tomorrow morning (in case my observations related to SOLR-9181+SOLR-9140
wind up being total flukes) before reverting.
> explosion of timeout related failures in jenkins the past few days
> ------------------------------------------------------------------
>
> Key: SOLR-9189
> URL: https://issues.apache.org/jira/browse/SOLR-9189
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
> Priority: Blocker
> Fix For: 6.1
>
>
> In the past few days, something has gone seriously wonky with our jenkins
> tests -- causing a serious explosion in the number of test failures --
> notably do to various sorts of timeouts...
> * "Unable to create core ... Timed out getting coreNodeName for ..."
> * "msg=SolrCore is loading,code=503"
> * "Timeout occured while waiting response from server"
> * "No registered leader was found after waiting for 30000ms"
> * "Unable to create core ... Caused by: Timed out getting shard id for core:
> ..."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
