Skip to content

Conversation

@wardlican
Copy link
Contributor

@wardlican wardlican commented Nov 17, 2025

Why are the changes needed?

In master-slave mode, the optimizer needs to support pulling optimization tasks from each ams node for processing.

Close #3928.

Brief change log

  1. In master-slave mode, the optimizer can pull tasks from each currently active AMS.
  2. In master-slave mode, the AMS automatically detects the addition and timeout of the optimizer from the database.

How was this patch tested?

  • Add some test cases that check the changes thoroughly including negative and positive cases if possible

  • Add screenshots for manual tests if appropriate

  • Run test locally before making a pull request

Documentation

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

wardli added 18 commits October 29, 2025 17:49
@github-actions github-actions bot added module:ams-server Ams server module module:ams-optimizer AMS optimizer module module:common labels Nov 17, 2025
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.

[Subtask]: Modify the optimizer to support obtaining tasks from each AMS node for processing.

1 participant