[
https://issues.apache.org/jira/browse/SOLR-14247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410370#comment-17410370
]
Mark Robert Miller commented on SOLR-14247:
-------------------------------------------
{quote}which (again for reasons i don't undestand) seems to be causing suite
level thread leaks of Log4j AsyncLogger threads
{quote}
I'm going to guess it's because log4j has not actually been shutdown for years.
Which must have bothered me a lot more than anyone else since I must have been
annoyed by it and fixed it 3-4 times since then. Though I guess to be fair,
when the tests regularly hang out for long periods doing nothing when they are
finished, that probably feels like a nice async shutdown much of the time.
> IndexSizeTriggerMixedBoundsTest does a lot of sleeping
> ------------------------------------------------------
>
> Key: SOLR-14247
> URL: https://issues.apache.org/jira/browse/SOLR-14247
> Project: Solr
> Issue Type: Bug
> Components: Tests
> Reporter: Mike Drob
> Assignee: Mike Drob
> Priority: Minor
> Fix For: main (9.0)
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When I run tests locally, the slowest reported test is always
> IndexSizeTriggerMixedBoundsTest coming in at around 2 minutes.
> I took a look at the code and discovered that at least 80s of that is all
> sleeps!
> There might need to be more synchronization and ordering added back in, but
> when I removed all of the sleeps the test still passed locally for me, so I'm
> not too sure what the point was or why we were slowing the system down so
> much.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
