[
https://issues.apache.org/jira/browse/SOLR-15644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419012#comment-17419012
]
Mark Robert Miller commented on SOLR-15644:
-------------------------------------------
It has nothing to do with lingering, lingering is configurable.
And yes, it’s slow. It’s slow because it’s generic and because what you
interrupt and when and whether and how you retry matters a lot.
I’ve dealt with it over and over in hundreds of non theoretical cases.
What I put in does nothing - nothing even calls it. It’s there to be used by
the issues that need it.
I’ve run the tests pretty much 100s of X faster than what they run here, I’ve
looked 100s of thread leak issues and how they interact with test framework and
what it offers.
And it has 0 to do with lingering. First thing I do whenever I touch these
tests seriously is turn that to 0.
> Add the ability to interrupt and wait for threads for problematic tests.
> ------------------------------------------------------------------------
>
> Key: SOLR-15644
> URL: https://issues.apache.org/jira/browse/SOLR-15644
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Tests
> Reporter: Mark Robert Miller
> Assignee: Mark Robert Miller
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The stuff in the test framework is slow and lacks control. For problematic
> tests, you don't want to linger first and you want fine control around
> interrupting - interrupting with a sledgehammer approach can actually make
> things take longer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
