-
Notifications
You must be signed in to change notification settings - Fork 658
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
Segmentation violation Error with confluent kafka GO sdk v2 #1260
Comments
We are also having similar issues with the Also what version are you using? Could this be related to confluentinc/librdkafka#4689 (and fixed in librdkafka v2.5)? I saw it mentions the .NET client crashing but it might be the Go one too. |
It doesn't look like librdkafka v2.5 fixes the issue. |
Downgrading to v2.3.0 seems to fix our issue. |
I'm facing the same problem. But in my case, I'm only using the package When upgrading from I'm able to fix the problem by downgrading the Is this error some kind on the roadmap? |
What I discover here is that my Docker Images are built using musl in a alpine based image with static link. When I build in this way, if I press Ctrl+C on terminal that is running the built binary, the crash happens.
|
Description
Team,
This is regarding a crash issue we are facing with confluent Kafka go SDK. Basically, we use GO “github.com/confluentinc/confluent-kafka-go/v2/kafka" SDK to connect to Kafka Admin client and then get all inventory topics name based on group name passed (Later we use this topics name to get all information related to Kafka topics consumer lags and we monitor those lags for each topics).
The. SDK crashes with below error.
SIGSEGV: segmentation violation
PC=0x599c240 m=3 sigcode=1 addr=0x0
signal arrived during cgo execution
This error is with GO confluent Kafka SDK V2.
How to reproduce
create kafka.NewAdminClient
// get all inventory topics name based on group name
describeGroupsResult, err := adminClient.DescribeConsumerGroups(ctx, []string{groupID}, kafka.SetAdminRequestTimeout(2*time.Second))
if err != nil {
log.Printf("Error while calling Describe consumer groups: %v", err)
return nil, err
}
This raise this segmentation error
Checklist
Please provide the following information:
ConfigMap{...}
SIGSEGV: segmentation violation
PC=0x599c240 m=3 sigcode=1 addr=0x0
signal arrived during cgo execution
goroutine 990 gp=0xc002534540 m=3 mp=0xc00008d008 [syscall]:
runtime.cgocall(0x58d8a50, 0xc028058550)
/home/ec2-user/go1.22.3/src/runtime/cgocall.go:157 +0x4b fp=0xc028058510 sp=0xc0280584d8 pc=0x40fe0b
github.com/confluentinc/confluent-kafka-go/v2/kafka._Cfunc_rd_kafka_Node_id(0x0)
_cgo_gotypes.go:2382 +0x4b fp=0xc028058550 sp=0xc028058510 pc=0x145e0eb
github.com/confluentinc/confluent-kafka-go/v2/kafka.(*AdminClient).cToConsumerGroupDescriptions.func8(0x0)
/home/ec2-user/valtix-sw/gosrc/pkg/mod/github.com/confluentinc/confluent-kafka-go/v2@v2.1.1/kafka/adminapi.go:853 +0x4d fp=0xc028058598 sp=0xc028058550 pc=0x146980d
[github.com/confluentinc/confluent-kafka-go/v2/kafka.(*AdminClient).cToConsumerGroupDescriptions(0xc028473e30](https://github.com/confluentinc/confluent-kafka-go/v2/kafka.(*AdminClient).cToConsumerGroupDescriptions(0xc028473e30), 0x7f1580058170, 0x1)
/home/ec2-user/valtix-sw/gosrc/pkg/mod/github.com/confluentinc/confluent-kafka-go/v2@v2.1.1/kafka/adminapi.go:853 +0x1f1 fp=0xc028058880 sp=0xc028058598 pc=0x1468bb1
[github.com/confluentinc/confluent-kafka-go/v2/kafka.(*AdminClient).DescribeConsumerGroups(0xc028473e30](https://github.com/confluentinc/confluent-kafka-go/v2/kafka.(*AdminClient).DescribeConsumerGroups(0xc028473e30), {0x7783608, 0x9f39c60}, {0xc028059190, 0x1, 0x1}, {0xc028059180, 0x1, 0x1})
/home/ec2-user/valtix-sw/gosrc/pkg/mod/github.com/confluentinc/confluent-kafka-go/v2@v2.1.1/kafka/adminapi.go:2078 +0x7b5 fp=0xc028058b40 sp=0xc028058880 pc=0x147b6b5
[github.com/valtixinc/valtix-sw/controller/kafkautils.GetConsumerLagForKafkaTopics({0x7783608](https://github.com/valtixinc/valtix-sw/controller/kafkautils.GetConsumerLagForKafkaTopics(%7B0x7783608), 0x9f39c60}, 0xc028473e30, {0xc002342100, 0x10})
)
Provide broker log excerpts
Critical issue Yes
The text was updated successfully, but these errors were encountered: