Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix for sync up job not working in 2.17 when upgraded from previous versions #3241

Merged
merged 2 commits into from
Dec 12, 2024

Conversation

rbhavna
Copy link
Collaborator

@rbhavna rbhavna commented Nov 27, 2024

Description

fix for sync up job not working in 2.17 when upgraded from previous versions

Related Issues

Resolves #3238

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@@ -261,6 +261,7 @@ private void queryRunningModels(ActionListener<SearchResponse> listener) {
private void triggerModelRedeploy(ModelAutoRedeployArrangement modelAutoRedeployArrangement) {
if (modelAutoRedeployArrangement == null) {
log.info("No more models in arrangement, skipping the redeployment");
redeployAModel();
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why should we redeploy the model if modelAutoRedeployArrangement is null?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This method calls for redeploying the next model. Not the same one. Ideally if this is null, this condition should have been satisfied and triggerModelRedeploy shouldn't be called. Alternatively we can call startCronjobAndClearListener() here as well.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Please change this to startCronjobAndClearListener method call.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Also, can you add an else to this if to ensure the cronjob started in edge cases, e.g. user deleted all the models in the index.

ylwu-amzn
ylwu-amzn previously approved these changes Dec 3, 2024
@rbhavna rbhavna had a problem deploying to ml-commons-cicd-env December 3, 2024 22:25 — with GitHub Actions Failure
@rbhavna rbhavna had a problem deploying to ml-commons-cicd-env December 3, 2024 23:54 — with GitHub Actions Failure
Signed-off-by: Bhavana Goud Ramaram <[email protected]>
@Zhangxunmt Zhangxunmt merged commit c2a40c1 into opensearch-project:main Dec 12, 2024
10 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Dec 12, 2024
…ersions (#3241)

* fix for sync up job not working in 2.17 when upgraded from previous versions

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

* add sync-up job in missing places

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

---------

Signed-off-by: Bhavana Goud Ramaram <[email protected]>
(cherry picked from commit c2a40c1)
opensearch-trigger-bot bot pushed a commit that referenced this pull request Dec 12, 2024
…ersions (#3241)

* fix for sync up job not working in 2.17 when upgraded from previous versions

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

* add sync-up job in missing places

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

---------

Signed-off-by: Bhavana Goud Ramaram <[email protected]>
(cherry picked from commit c2a40c1)
opensearch-trigger-bot bot pushed a commit that referenced this pull request Dec 12, 2024
…ersions (#3241)

* fix for sync up job not working in 2.17 when upgraded from previous versions

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

* add sync-up job in missing places

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

---------

Signed-off-by: Bhavana Goud Ramaram <[email protected]>
(cherry picked from commit c2a40c1)
tkykenmt pushed a commit to tkykenmt/ml-commons that referenced this pull request Dec 15, 2024
…ersions (opensearch-project#3241)

* fix for sync up job not working in 2.17 when upgraded from previous versions

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

* add sync-up job in missing places

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

---------

Signed-off-by: Bhavana Goud Ramaram <[email protected]>
tkykenmt pushed a commit to tkykenmt/ml-commons that referenced this pull request Dec 15, 2024
…ersions (opensearch-project#3241)

* fix for sync up job not working in 2.17 when upgraded from previous versions

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

* add sync-up job in missing places

Signed-off-by: Bhavana Goud Ramaram <[email protected]>

---------

Signed-off-by: Bhavana Goud Ramaram <[email protected]>
Signed-off-by: tkykenmt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Sync up job not working as expected when upgrading cluster from prev versions to 2.17
5 participants