Skip to content

Conversation

jan-elastic
Copy link
Contributor

No description provided.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

clusterService.removeListener(this);
stopScheduling();
metrics.close();
scalers.clear();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've leave the metrics list as is and don't recreate them (which leads to errors).

Clearing the scalers collection, so that the metrics do not observe anything anymore.

Copy link
Member

@davidkyle davidkyle left a comment

Choose a reason for hiding this comment

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

LGTM

@jan-elastic jan-elastic added auto-backport Automatically create backport pull requests when merged and removed v7.0.0 labels Oct 14, 2024
@jan-elastic jan-elastic merged commit 0c02c2b into main Oct 14, 2024
17 checks passed
@jan-elastic jan-elastic deleted the aa-fix-metrics branch October 14, 2024 15:16
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

An unexpected error occurred when attempting to backport this PR.

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 114721

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged backport pending >bug :ml Machine learning >non-issue Team:ML Meta label for the ML team v8.16.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants