Closed bluesky9527520 closed 4 months ago
Hello! Thank you for filing an issue.
If this is a bug report, please include relevant logs to help us debug the problem.
Join slack 🤖 to connect and communicate with our developers.
github.com/openimsdk/open-im-server/v3/pkg/common/kafka.(MConsumerGroup).RegisterHandleAndConsumer(0xc0000a2e00, {0x17309a0, 0xc0000af180}) /openim/openim-server/pkg/common/kafka/consumer_group.go:71 +0x145 created by github.com/openimsdk/open-im-server/v3/internal/msgtransfer.(MsgTransfer).Start /openim/openim-server/internal/msgtransfer/init.go:114 +0x1ea panic: kafka: client has run out of available brokers to talk to
Kafka has crashed, please check the server's memory and disk space, and verify if there are different applications running on it.
It is recommended to update to version 3.5.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
The Docker deployment plan has been fully upgraded. Please refer to the README for the new scheme. The new scheme is simpler to use and supports Linux, Windows, and Mac.
What would you like to share?
The openim server component will become unhealthy after a few days, return to normal after restarting, and then become unhealthy again after a few days, repeatedly. At first, I thought there was not enough memory, but increasing the memory to 8GB still couldn't solve the problem. The attachment is a log file from the past month, please review it.
Thanks! imserverlogs.zip
Additional information
No response