Clean up clusters between tests#41187
Conversation
This PR adds additional cleanup when stopping the node. The data dir is excepted because it gets reused in some tests. Without this cleanup the number of working dir copies could grew to exhaust all available disk space.
|
Pinging @elastic/es-core-infra |
|
@elasticmachine run elasticsearch-ci/2 |
rjernst
left a comment
There was a problem hiding this comment.
This looks ok for now, but I wonder if we should not do this for the run task. I often use this as a way to quickly get a runnable built directory, going into the extracted dir to make local modifications and manually run elasticsearch.
|
I'll merge this now and look at run lather. |
This PR adds additional cleanup when stopping the node. The data dir is excepted because it gets reused in some tests. Without this cleanup the number of working dir copies could grew to exhaust all available disk space.
This PR adds additional cleanup when stopping the node. The data dir is excepted because it gets reused in some tests. Without this cleanup the number of working dir copies could grew to exhaust all available disk space.
This PR adds additional cleanup when stopping the node. The data dir is excepted because it gets reused in some tests. Without this cleanup the number of working dir copies could grew to exhaust all available disk space.
|
@rjernst I looked at |
This reverts commit 78e7f4a.
This reverts commit 4712075.
This reverts commit 44a0c46.
This reverts commit a795069.
|
This change had the the unfortunate side effect of deleting the test cluster log files which are vital for debugging tests. I reverted the change on all 4 branches master: 9efc853 Another problem is that the clean up code removes files but the directories are left intact. For example the |
This reverts commit 78e7f4a.
This reverts commit 9efc853.
This PR adresses the same concern as elastic#41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
* Revert "Revert "Clean up clusters between tests (#41187)"" This reverts commit 9efc853. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as #41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
* Revert "Revert "Clean up clusters between tests (#41187)"" This reverts commit 9efc853. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as #41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
* Revert "Revert "Clean up clusters between tests (#41187)"" This reverts commit 9efc853. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as #41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
* Revert "Revert "Clean up clusters between tests (#41187)"" This reverts commit 9efc853. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as #41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
* Revert "Revert "Clean up clusters between tests (#41187)"" This reverts commit 9efc853. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as #41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
This PR adds additional cleanup when stopping the node. The data dir is excepted because it gets reused in some tests. Without this cleanup the number of working dir copies could grew to exhaust all available disk space.
This reverts commit 78e7f4a.
* Revert "Revert "Clean up clusters between tests (elastic#41187)"" This reverts commit 9efc853. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as elastic#41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy.
This PR adds additional cleanup when stopping the node.
The data dir is excepted because it gets reused in some tests.
Without this cleanup the number of working dir copies could grew to
exhaust all available disk space.