[
https://issues.apache.org/jira/browse/SOLR-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829682#comment-15829682
]
Alan Woodward commented on SOLR-10001:
--------------------------------------
>From going through the logs, it seems that the test is likely to fail if
>testAddAndRemoveRole() gets run early on. This test adds the 'overseer' role
>to a node, and then removes it, but it doesn't wait for the overseer status to
>change. So if the next test tries to create a new collection, then we can get
>the overseer quitting in the middle of the creation command, leading to
>timeouts while the nodes all wait for each other to sort themselves out.
In general, if users are doing things like forceably changing Overseers, then
they shouldn't be trying to run other cluster operations at the same time, so I
think we're fine to fix this by making the test wait for the new Overseer to
take over.
> CollectionsAPISolrJTest failures
> --------------------------------
>
> Key: SOLR-10001
> URL: https://issues.apache.org/jira/browse/SOLR-10001
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Alan Woodward
> Assignee: Alan Woodward
>
> This test has failed quite a few times recently:
> https://jenkins.thetaphi.de/job/Lucene-Solr-6.4-Linux/25/
> https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/18801/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
