[
https://issues.apache.org/jira/browse/SOLR-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109972#comment-14109972
]
Hoss Man commented on SOLR-6416:
--------------------------------
it waits 30 seconds for the processor to do what it says it will do and
"expire" the doc (ie: delete it)
the reason we wait 30 seconds (instead of something smaller) is because we need
to give enough time for the doc to be added and be able to verify the doc is
there -- if we tighten up the time to something smaller, we could easily get
false failures where the doc is added, then expired/deleted before we ever
verify the initial add. (and if we don't verify the document is added properly,
we'd get false positives thinking hte doc was deleted when it actually had a
problem being added in the first place)
i'm open to suggestions for improvements -- but at the end of the day, what
we're testing is that: 1) a Timer is created; b) that the timer fires; c) that
a certain action happens. we can make the timer duration as short as you want,
but the current "slowness" exists because w/shorter durations it's trivial to
get false successes and false failures. (which is why it's documented as
{{\@Slow}}
> DistribDocExpirationUpdateProcessorTest is pretty slow in non nightly test
> runs.
> --------------------------------------------------------------------------------
>
> Key: SOLR-6416
> URL: https://issues.apache.org/jira/browse/SOLR-6416
> Project: Solr
> Issue Type: Sub-task
> Components: Tests
> Reporter: Mark Miller
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
