Resiliency: Add basic upgrade test script #7074
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM This is also a nice (expert) example of using the Python client. Thank you for upgrading to Python 3 and adding the install instructions; I was able to run this successfully! For some reason I struggle to install elasticsearch python client under Python 2.x: I hit a strange exception from "pip install elasticsearch". |
|
Worked for me on both python 2.6.1 and 3.4.0. Would be nice to have a message confirming that everything went well on the standard out when the test ends? |
|
LGTM |
|
Tested it with python 2.7 and 3.4 and it works well. LGTM |
This commit adds a basic full cluster restart upgrade script that tests upgrades of elasticsearch across major version. In contrast to the BWC tests we are running using the java test framework this test uses a python script as well as the REST APIs to ensure upgrades across major version work and indices are compatible. The upgrade test starts 2 or more nodes of an old elasticserach version, indexes a random number of documents into the running nodes and executes a full cluster restart. After the nodes are recovered a small set of basic checks are executed to ensure all documents are still searchable and field data can be loaded etc. Closes elastic#7074
s1monw
added a commit
that referenced
this pull request
Jul 29, 2014
This commit adds a basic full cluster restart upgrade script that tests upgrades of elasticsearch across major version. In contrast to the BWC tests we are running using the java test framework this test uses a python script as well as the REST APIs to ensure upgrades across major version work and indices are compatible. The upgrade test starts 2 or more nodes of an old elasticserach version, indexes a random number of documents into the running nodes and executes a full cluster restart. After the nodes are recovered a small set of basic checks are executed to ensure all documents are still searchable and field data can be loaded etc. Closes #7074
clintongormley
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds a basic full cluster restart upgrade script that tests
upgrades of elasticsearch across major version. In contrast to the BWC
tests we are running using the java test framework this test uses a python
script as well as the REST APIs to ensure upgrades across major version work and
indices are compatible.
The upgrade test starts 2 or more nodes of an old elasticserach version, indexes
a random number of documents into the running nodes and executes a full cluster restart.
After the nodes are recovered a small set of basic checks are executed to ensure all
documents are still searchable and field data can be loaded etc.