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

[Enhancement] Optimize pop log level #8281

Closed
1 task done
drpmma opened this issue Jun 11, 2024 · 0 comments · Fixed by #8282
Closed
1 task done

[Enhancement] Optimize pop log level #8281

drpmma opened this issue Jun 11, 2024 · 0 comments · Fixed by #8282
Assignees
@drpmma
Labels
type/enhancement

Comments

@drpmma
Copy link
Contributor

drpmma commented Jun 11, 2024 •
edited
Loading

Before Creating the Enhancement Request

  • I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

change pop log level to debug when all the revive messages are handled

Motivation

There are too many pop logs

Describe the Solution You'd Like

change pop log level to debug when all the revive messages are handled

Describe Alternatives You've Considered

No

Additional Context

No response
@drpmma drpmma self-assigned this Jun 11, 2024
@drpmma drpmma mentioned this issue Jun 11, 2024
Merged
drpmma added a commit that referenced this issue Jun 13, 2024
@drpmma
[ISSUE #8281] Optimize pop log level (#8282)
3ac5c73 
* change pop log level to debug when all the revive messages are handled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@drpmma drpmma

Labels
type/enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ISSUE #8281] Optimize pop log level drpmma/rocketmq
1 participant
@drpmma