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

[Bug][Manager] Offline data sync may create too many scheduling instances at the start point #10754

Closed
2 tasks done
aloyszhang opened this issue Aug 6, 2024 · 0 comments · Fixed by #10755
Closed
2 tasks done
Assignees
Labels
type/bug Something is wrong
Milestone

Comments

@aloyszhang
Copy link
Contributor

What happened

When configuring an offline data sync with crontab scheduling, there may be too many scheduling instances (Flink batch job), including instances before the current time.

What you expected to happen

The schedule instances before the current time should not be generated.

How to reproduce

  1. add an inlong group for offline sync with crontab expression in which the start time is before the current time in the schedule info by open API
  2. submit the group and approve it
  3. the scheduling instances before the current time are also generated

Environment

No response

InLong version

master

InLong Component

InLong Manager

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something is wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant