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

Print log when failed to send heartbeat #1002

Closed
cserwen opened this issue Feb 15, 2023 · 0 comments · Fixed by #1003
Closed

Print log when failed to send heartbeat #1002

cserwen opened this issue Feb 15, 2023 · 0 comments · Fixed by #1003
Labels
log

Comments

@cserwen
Copy link
Member

cserwen commented Feb 15, 2023

BUG REPORT

  1. Please describe the issue you observed:
    This log was printed when failed to send heartbeat.
send heart beat to broker failed,brokerName=rocketmq-raft0,brokerId=3,brokerAddr="192.168.123.1:10911",responseCode=1

And remark should also be printed to find the root cause, like this

send heart beat to broker failed,brokerName=rocketmq-raft0,brokerId=3,brokerAddr="192.168.123.1:10911",responseCode=1 ,remark="org.apache.rocketmq.acl.common.AclException: No default permission for topic:TopicTest"

  1. Please tell us about your environment:

    • What is your OS?

    • What is your client version?

    • What is your RocketMQ version?

  2. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
@cserwen cserwen mentioned this issue Feb 15, 2023
Merged
5 tasks
francisoliverlee pushed a commit that referenced this issue Mar 13, 2023
Merge pull request #1003 from cserwen/heartbeat_github
56d1a7d 
[ISSUE #1002] fix: add log when send heartbeat failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
log
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ISSUE #1002] fix: add log when send heartbeat failed cserwen/rocketmq-client-go
2 participants
@francisoliverlee @cserwen