[ML] Improve log message for model snapshot update #134541
Merged
Conversation
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
elasticsearchmachine
added
needs:triage
valeriy42
added
v9.1.4
v8.19.4
v8.18.8
v9.0.8
:ml
|
Pinging @elastic/ml-core (Team:ML) |
valeriy42
requested review from
DaveCTurner and
davidkyle
and removed request for
DaveCTurner
DaveCTurner
reviewed
Sep 11, 2025
...rc/main/java/org/elasticsearch/xpack/ml/job/process/autodetect/JobModelSnapshotUpgrader.java
Outdated
Show resolved
Hide resolved
…ub.com/valeriy42/elasticsearch into bug/1650-delete-snapshot-error-message
DaveCTurner
reviewed
Sep 11, 2025
server/src/main/java/org/elasticsearch/common/ReferenceDocs.java
Outdated
Show resolved
Hide resolved
DaveCTurner
reviewed
Sep 11, 2025
server/src/main/java/org/elasticsearch/common/ReferenceDocs.java
Outdated
Show resolved
Hide resolved
valeriy42
changed the title
valeriy42
added
the
auto-backport
💔 Backport failed
You can use sqren/backport to manually backport by running |
mridula-s109
pushed a commit
to mridula-s109/elasticsearch
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue.
valeriy42
added a commit
to valeriy42/elasticsearch
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c)
This was referenced Sep 17, 2025
valeriy42
added a commit
to valeriy42/elasticsearch
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c) # Conflicts: # server/src/main/java/org/elasticsearch/common/ReferenceDocs.java # server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
valeriy42
added a commit
to valeriy42/elasticsearch
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c) # Conflicts: # server/src/main/java/org/elasticsearch/common/ReferenceDocs.java # server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt
valeriy42
added a commit
to valeriy42/elasticsearch
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c) # Conflicts: # server/src/main/java/org/elasticsearch/common/ReferenceDocs.java # server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c) # Conflicts: # server/src/main/java/org/elasticsearch/common/ReferenceDocs.java # server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c) # Conflicts: # server/src/main/java/org/elasticsearch/common/ReferenceDocs.java # server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c) # Conflicts: # server/src/main/java/org/elasticsearch/common/ReferenceDocs.java # server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 17, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue. (cherry picked from commit c47522c)
gmjehovich
pushed a commit
to gmjehovich/elasticsearch
that referenced
this pull request
Sep 18, 2025
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade. Step to reproduce: setup a 7.17 cluster create and start an anomaly detection job upgrade to 8.18 or 8.19 go to upgrade assistant change .ml-anomalies-shared to read only then try upgrade obsolete model snapshot Observed: upgrade model snapshot will fail. This PR extends the warning message explaining the steps to resolve the issue.
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.
Since the 9.0 upgrade, we have introduced a solution by setting large .ml-anomalies to read only during the upgrade assistant. However, there is an edge case that will cause the obsolete model snapshot to fail to upgrade.
Step to reproduce:
Observed:
This PR extends the warning message explaining the steps to resolve the issue.