[SOLR-11949] Create Time Routed Alias stress-test

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: SolrCloud
• Assignee: Unassigned
• Reporter: David Smiley
• Created: 06/Feb/18 05:04
• Updated: 01/May/18 01:49

Description

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).

Issue Links

• is related to: SOLR-12295 Time Routed Aliases: Delete obsolete collections Async