Cluster formation with ref counting - part1#31658
Closed
alpar-t wants to merge 7 commits intoelastic:masterfrom
Closed
Cluster formation with ref counting - part1#31658alpar-t wants to merge 7 commits intoelastic:masterfrom
alpar-t wants to merge 7 commits intoelastic:masterfrom
Conversation
``` > Task :plugins:ingest-user-agent:listElasticSearchClusters Starting cluster: myTestCluster * myTestCluster: /home/alpar/work/elastic/elasticsearch/plugins/ingest-user-agent/foo Asked to unClaimAndStop myTestCluster, since cluster still has 1 claim it will not be stopped > Task :plugins:ingest-user-agent:testme UP-TO-DATE Stopping myTestCluster, since no of claims is 0 ``` Meant to auto manage the plugins in the backround.
Use the version to configure cluster formation with Version and Distribution for convenience
Collaborator
|
Pinging @elastic/es-core-infra |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 is one of many parts paving the way to a cluster formation that manages the clusters without Gradle tasks ( but it does use Gradle "services" ) - e.x. for copying, executing etc.
The plugin is not yet used other than in integration tests, and doesn't do anything useful yet, but it does prove that the ref counting works well with Gradle and that the public APIs are sufficient to implement it.
In addition, the
Versionclass was implemented in java so the cluster formation config can work with it.This is part of: #30904