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.

Sign up for GitHub

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

Jump to bottom

[Improvement]: The planning interval is too long and too many tasks are in pending state. After the log level is changed, the planning recovers #3194

Closed
2 of 3 tasks
Tracked by #3123
w724457655 opened this issue Sep 11, 2024 · 0 comments · Fixed by #3212
Closed
2 of 3 tasks
Tracked by #3123

[Improvement]: The planning interval is too long and too many tasks are in pending state. After the log level is changed, the planning recovers #3194

w724457655 opened this issue Sep 11, 2024 · 0 comments · Fixed by #3212
Assignees
@Aireed
Labels
type:improvement

Comments

@w724457655
Copy link

Search before asking

  • I have searched in the issues and found no similar issues.

What would you like to be improved?

In the process of using, we found that the planning time of the table is too long, and all the tables skipped (table entry 5w+) will be printed in the log
image

Relief after adjusting the log level to error (originally info)
image

How should we improve?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Aireed Aireed

Labels
type:improvement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[AMORO-3194]improvement: optimize plan log print Aireed/amoro
2 participants
@Aireed @w724457655