[ 
https://issues.apache.org/jira/browse/SOLR-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570330#comment-13570330
 ] 

Mark Miller commented on SOLR-4401:
-----------------------------------

bq. prior art in TestReplicationHandler?

Not specifically I don't think, but it's probably an option - lot's of prior 
art to go around that should fit this.

I think largely you can keep the machinery as it is. You probably want to use 
JettySolrRunner to take the place of starting up Solr (currently a user 
action). Extend SolrTestCase4j but don't call initCore. Then the tmp directory 
should be chosen in a manner similar to other tests. Then add some asserts, 
some polish, and I think it may be a fairly easy job.

* Also, tag as nightly? Weekly?

I think it should actually be run frequently for short intervals - like 30 
seconds - and then long runs more like nightly or weekly.
                
> Move the stress test in SOLR-4196 into a junit test
> ---------------------------------------------------
>
>                 Key: SOLR-4401
>                 URL: https://issues.apache.org/jira/browse/SOLR-4401
>             Project: Solr
>          Issue Type: Test
>    Affects Versions: 4.2, 5.0
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Minor
>             Fix For: 4.2, 5.0
>
>         Attachments: StressTest.zip
>
>
> As part of SOLR-4196, I created a stress test proces for rapidly opening and 
> closing cores. It'd probably be useful to make this into a junit test that 
> ran nightly (it needs some time in order to show anything, as in minutes). 
> Typical failures are 20 minutes into the run, but occasionally they're faster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to