David Smiley created SOLR-11949:
-----------------------------------
Summary: Create Time Routed Alias stress-test
Key: SOLR-11949
URL: https://issues.apache.org/jira/browse/SOLR-11949
Project: Solr
Issue Type: Sub-task
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Reporter: David Smiley
It would be nice to have a scalability test / stress test of sorts for Time
Routed Aliases to help identify any problems that may exist. At least at the
moment, I'm thinking of a test that would never get run automatically (by say
Jenkins or "ant test"), but I could change my mind. We already have some TRA
tests of course but except for one of them, the tests are more about
functionality rather than proving out possible race conditions & other
scalability bugs.
Something that creates one TRA up front then beats on it for awhile, then shuts
down
* configurable # nodes, and TRA statistics. Maybe 10-sec interval collections,
with deleting collections older than a minute.
* May randomly update the interval part-way through
* sends data in multiple threads.
* sends data to nodes randomly via HttpSolrClient or ConcurrentUpdateSolrClient
or CloudSolrClient randomly (test infra can do this already except CUSC), or
* sends data in batches of configurable sizes.
* at the end verifies that the collections only hold the documents they should
(one of my TRA tests has code that can be used here)
Using this test, it'd be interesting to see what happens when a core for the
oldest collection is receiving documents while simultaneously it is getting
deleted (for being old).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
