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

[Enhancement] Optimise consumer message printing #8621

Open
1 task done
weihubeats opened this issue Sep 2, 2024 · 1 comment · May be fixed by #8642
Open
1 task done

[Enhancement] Optimise consumer message printing #8621

weihubeats opened this issue Sep 2, 2024 · 1 comment · May be fixed by #8642

Comments

@weihubeats
Copy link
Member

Before Creating the Enhancement Request

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

Summary

Optimise consumer message printing

  • pre-optimisation
2024-09-02 10:51:29.132 INFO  [10] [MQClientFactoryScheduledThread] [o.a.r.c.c.s.RemoteBrokerOffsetStore#persistAll:129] - [persistAll] Group: GID-TEST-TOPIC ClientId: 10.0.0.10@10#18239483154204429 updateConsumeOffsetToBroker MessageQueue [topic=test-topic, brokerName=broker-a, queueId=1] 456
  • post-optimisation
2024-09-02 10:51:29.132 INFO  [10] [MQClientFactoryScheduledThread] [o.a.r.c.c.s.RemoteBrokerOffsetStore#persistAll:129] - [persistAll] Group: GID-TEST-TOPIC ClientId: 10.0.0.10@10#18239483154204429 updateConsumeOffsetToBroker MessageQueue [topic=test-topic, brokerName=broker-a, queueId=1] offset: 456

Motivation

Optimise the printing of consumer messages to make the log look clearer

Describe the Solution You'd Like

Add more description

Describe Alternatives You've Considered

no

Additional Context

No response

@assertion
Copy link

assertion commented Sep 4, 2024

I'll fix this issue.

@assertion assertion linked a pull request Sep 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants