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

kafka: error decoding packet: invalid array length #2524

Closed
yehaotong opened this issue Jul 25, 2023 · 9 comments
Closed

kafka: error decoding packet: invalid array length #2524

yehaotong opened this issue Jul 25, 2023 · 9 comments
Labels
stale Issues and pull requests without any recent activity

Comments

@yehaotong
Copy link

[[[[##### Versions

Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.

Sarama Kafka Go
Configuration

What configuration values are you using for Sarama and Kafka?

Logs

When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.

logs: CLICK ME

Problem Description

](kafka: error decoding packet: invalid array length)]

@dnwe
Copy link
Collaborator

dnwe commented Jul 25, 2023

@yehaotong this generally means that the server has sent a response in a version that we don’t yet understand or haven’t correctly added support for, but we’d need to know your config settings, your broker version(s) and some sarama debug logs as per the issue template

@yehaotong
Copy link
Author

@yehaotong this generally means that the server has sent a response in a version that we don’t yet understand or haven’t correctly added support for, but we’d need to know your config settings, your broker version(s) and some sarama debug logs as per the issue template

I use the kafka-exporter to scrape kafka metrics, and it miss some consumergroup metric,and I find the log on the kafka-exporter: Cannot get consumer group: kafka: error decoding packet: invalid array length

@yehaotong
Copy link
Author

@yehaotong this generally means that the server has sent a response in a version that we don’t yet understand or haven’t correctly added support for, but we’d need to know your config settings, your broker version(s) and some sarama debug logs as per the issue template

the sarama version is: 1.38.1 , and the kafka version is: confluentinc/cp-kafka:5.0.3

@dnwe
Copy link
Collaborator

dnwe commented Jul 25, 2023

Hmm, I know the DescribeGroups response is somewhat undocumented in the member metadata area. I did fixup some issues in #2111 in the past but it sounds like kafka-exporter would already have that fix

@dnwe
Copy link
Collaborator

dnwe commented Jul 25, 2023

cp-kafka:5.0.3, so Kafka 2.0.1 afaik. What clients do you have connected to your (missing) consumer group?

@yehaotong
Copy link
Author

cp-kafka:5.0.3, so Kafka 2.0.1 afaik. What clients do you have connected to your (missing) consumer group?

what is mean clients connected to consumer group?
the missing consumer group can still scrape a few days ago, but at a certain moment, some indicators of the consumer group are all lost at the same time,and log begins to appear Cannot get consumer group: kafka: error decoding packet: invalid array length

@dnwe
Copy link
Collaborator

dnwe commented Jul 25, 2023

My guess is that something about the metadata recorded by the consumers in the group is causing the decoding error when Sarama describes it, but I’m not sure what clients you are using in the group to actually consume the messages

@yehaotong
Copy link
Author

My guess is that something about the metadata recorded by the consumers in the group is causing the decoding error when Sarama describes it, but I’m not sure what clients you are using in the group to actually consume the messages

How should I verify if there are any issues with the metadata you mentioned

@github-actions
Copy link

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

@github-actions github-actions bot added the stale Issues and pull requests without any recent activity label Oct 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues and pull requests without any recent activity
Projects
None yet
Development

No branches or pull requests

2 participants