[ https://issues.apache.org/jira/browse/SOLR-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884390#comment-16884390 ]
ASF subversion and git services commented on SOLR-13616: -------------------------------------------------------- Commit 7ddba3b7123f11d387ff395516cf46c607ac21ee in lucene-solr's branch refs/heads/master from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=7ddba3b ] Harden DeleteReplicaTest * tighten assertions related to type of watcher that should be removed * use waitForActiveCollection before deleting collections to work around SOLR-13616 and/or SOLR-13627 > Possible racecondition/deadlock between collection DELETE and PrepRecovery ? > (TestPolicyCloud failures) > ------------------------------------------------------------------------------------------------------- > > Key: SOLR-13616 > URL: https://issues.apache.org/jira/browse/SOLR-13616 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Hoss Man > Priority: Major > Attachments: SOLR-13616.test-incomplete.patch, > thetaphi_Lucene-Solr-master-Linux_24358.log.txt > > > Based on some recent jenkins failures in TestPolicyCloud, I suspect there is > a possible deadlock condition when attempting to delete a collection while > recovery is in progress. > I haven't been able to identify exactly where/why/how the problem occurs, but > it does not appear to be a test specific problem, and seems like it could > potentially affect anyone unlucky enough to issue poorly timed DELETE. > Details to follow in comments... -- This message was sent by Atlassian JIRA (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org