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

[AMORO-3111]Avoid optimization state blocking in planning #3115

Merged
merged 3 commits into from
Sep 14, 2024

Conversation

rfyu
Copy link
Contributor

@rfyu rfyu commented Aug 19, 2024

Why are the changes needed?

Close #3111.

Brief change log

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)

@github-actions github-actions bot added the module:ams-server Ams server module label Aug 19, 2024
@rfyu rfyu changed the title [WIP][AMORO-3111]Avoid optimization state blocking in planning [AMORO-3111]Avoid optimization state blocking in planning Sep 10, 2024
Copy link
Contributor

@zhoujinsong zhoujinsong left a comment

Choose a reason for hiding this comment

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

@rfyu Thanks for the contribution, I left some comments, PTAL.

} catch (Exception e) {
OptimizingStatus originalStatus = optimizingStatus;
updateOptimizingStatus(OptimizingStatus.PENDING);
LOG.error(
Copy link
Contributor

Choose a reason for hiding this comment

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

Warn logging level may be proper here.

@@ -299,7 +299,7 @@ public class AmoroManagementConf {
public static final ConfigOption<Long> DB_CONNECT_MAX_WAIT_MILLIS =
ConfigOptions.key("database.connection-pool-max-wait-millis")
.longType()
.defaultValue(1000L)
.defaultValue(-1L)
Copy link
Contributor

Choose a reason for hiding this comment

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

We may need to roll back the change here.

Copy link
Contributor

@zhoujinsong zhoujinsong left a comment

Choose a reason for hiding this comment

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

LGTM.

@zhoujinsong zhoujinsong merged commit 292111f into apache:master Sep 14, 2024
4 checks passed
zhoujinsong pushed a commit that referenced this pull request Oct 11, 2024
* Avoid optimization state blocking in planning

* modify the optimizing status in memory

* fix conflict and rollback configuration

(cherry picked from commit 292111f)
Signed-off-by: zhoujinsong <zhoujinsong0505@163.com>
XBaith pushed a commit to XBaith/amoro that referenced this pull request Dec 10, 2024
* Avoid optimization state blocking in planning

* modify the optimizing status in memory

* fix conflict and rollback configuration

(cherry picked from commit 292111f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module:ams-server Ams server module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Optimization state blocking in planning
2 participants