Skip to content

Clean up clusters between tests#41187

Merged
alpar-t merged 1 commit intoelastic:masterfrom
alpar-t:reduce-bwc-disk
Apr 18, 2019
Merged

Clean up clusters between tests#41187
alpar-t merged 1 commit intoelastic:masterfrom
alpar-t:reduce-bwc-disk

Conversation

@alpar-t
Copy link
Copy Markdown
Contributor

@alpar-t alpar-t commented Apr 15, 2019

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.
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-core-infra

@alpar-t alpar-t requested a review from mark-vieira April 15, 2019 08:29
@alpar-t
Copy link
Copy Markdown
Contributor Author

alpar-t commented Apr 15, 2019

@elasticmachine run elasticsearch-ci/2

Copy link
Copy Markdown
Member

@rjernst rjernst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@colings86 colings86 added v6.7.3 and removed v6.7.2 labels Apr 17, 2019
Copy link
Copy Markdown
Contributor

@mark-vieira mark-vieira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@alpar-t
Copy link
Copy Markdown
Contributor Author

alpar-t commented Apr 18, 2019

I'll merge this now and look at run lather.

@alpar-t alpar-t merged commit 78e7f4a into elastic:master Apr 18, 2019
alpar-t added a commit that referenced this pull request Apr 18, 2019
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.
alpar-t added a commit that referenced this pull request Apr 18, 2019
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.
alpar-t added a commit that referenced this pull request Apr 18, 2019
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.
@alpar-t
Copy link
Copy Markdown
Contributor Author

alpar-t commented Apr 18, 2019

@rjernst I looked at run but I think that will continue to work, since it runs in the foreground, it just stops when you interrupt it, so the cleanup won't happen.

@colings86 colings86 added v6.7.2 and removed v6.7.3 labels Apr 24, 2019
davidkyle added a commit that referenced this pull request Apr 25, 2019
davidkyle added a commit that referenced this pull request Apr 25, 2019
davidkyle added a commit that referenced this pull request Apr 25, 2019
davidkyle added a commit that referenced this pull request Apr 25, 2019
@davidkyle
Copy link
Copy Markdown
Member

davidkyle commented Apr 25, 2019

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
7.x 31d5a5a
7.0 1980b70
6.7 460333d

Another problem is that the clean up code removes files but the directories are left intact. For example the jdk directory and all its sub-directories remain but are empty.

akhil10x5 pushed a commit to akhil10x5/elasticsearch that referenced this pull request May 2, 2019
@alpar-t alpar-t deleted the reduce-bwc-disk branch May 2, 2019 11:20
alpar-t added a commit to alpar-t/elasticsearch that referenced this pull request May 2, 2019
alpar-t added a commit to alpar-t/elasticsearch that referenced this pull request May 2, 2019
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.
alpar-t added a commit that referenced this pull request May 6, 2019
* 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.
alpar-t added a commit that referenced this pull request May 6, 2019
* 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.
alpar-t added a commit that referenced this pull request May 6, 2019
* 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.
alpar-t added a commit that referenced this pull request May 6, 2019
* 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.
alpar-t added a commit that referenced this pull request May 6, 2019
* 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.
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
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.
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
* 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.
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants