Note: Forked from https://github.com/viveknarang/solr-upgrade-tests
The purpose of this program is to test rolling upgrades for Solr Cloud.
Upgraded version >> | 5.3.0 | 5.3.1 | 5.3.2 | 5.4.0 | 5.4.1 |
---|---|---|---|---|---|
5.2.1 | PASS | PASS | |||
5.3.0 | PASS | FAIL | FAIL | ||
5.3.1 | PASS | FAIL | FAIL | ||
5.3.2 | FAIL | FAIL | |||
5.4.0 | PASS |
Logs for 5.3.2 to 5.4.1: http://106.186.125.89/logs.tar.gz
Use the following command to run this program on server
mvn clean compile assembly:single
java -jar target/org.apache.solr.tests.upgradetests-0.0.1-SNAPSHOT-jar-with-dependencies.jar -v1 5.3.0 -v2 5.4.1 -Nodes 3 -Shards 2 -Replicas 3
-v1 {Version One} Example 5.4.0
-v2 {Version Two} Example 5.4.1
-Nodes {Number of nodes} Example 3
-Shards {Number of shards} Example 2
-Replicas {Number of Replicas} Example 3
Following is the summary of the steps that the program follows to test the rolling upgrade
- Start ZK
- Start Solr nodes
- Create a Test collection
- Insert a set of 1000 documents
- Stop each node one by one, upgrade each node by replacing lib/ folder and webapp/ folder on server and then start each node
- Check if the /live_nodes has the upgraded node
- Check if all the documents are available from the collection
- If 6 and 7 pass, the program identifies the test as successful
- Upon failure of either 6 or 7, the program declares the test as failed
- If test passed, shutdown the nodes and cleaning zookeeper data
- Running against unreleased (master/branch_5x)
- Making it easier to add more tests to this framework
- Code cleanup.
- Have ability to specify any version of SolrJ to be used in the tests. (Currently, this is hardcoded in the pom.xml, which should be easy to change configurably).